It works, thank you very much :)
Two more questions:
1) If I want to make color1 fully transparent, I guess using the color alpha
channel wont work, so maybe I have to make a custom shader to discard color1
pixels? Or do you have any other sugestions ?
2) Is there a equivalent to OpenGL
On Fri, 28 May 2021, Jason H wrote:
> console.log("result:", JSON.stringify(App.result)); // this does not
> qrc:/screens/Result.qml:32: TypeError: Type error
My copy of ECMA-262, 5ᵗʰ edition, has JSON.stringify fail
(in the “abstract operation JO”, p.205, last ordered list
on the page, step 1)
I've got a really weird error:
qml: type: object [DEBUG-12344567890,N]
qrc:/screens/Result.qml:32: TypeError: Type error
The statements are:
console.log("type:", typeof App.result, Object.keys(App.result)) // this works
console.log("result:", JSON.stringify(App.result)); // this does not
App is
Hi,
The custom geometry lacks UV coordinates in your example application, and so it
samples with texture coordinates (0, 0) for any fragment, hence getting a line
with color0 instead of the expected color0-color1-color0-...
Add two floats per vertex and register an attribute for TexCoord0:
Yea man, just change it. No one remembers a coward! :)
Den fre 28 maj 2021 kl 17:07 skrev David M. Cotter :
>
> assuming your change "does the right thing in all cases" then i think it
> should be the default.
>
> nobody WANTS the currently-bad behavior.
>
> -dave
>
> > On May 28, 2021, at 5:55
Here, we have had an issue when switching from 5.11.1 to 5.15.2, with multi
selection and dragNdrop
Now, if we start a drag n drop, but previously clicked on the item a short
time ago (less than the double click delay), then the view starts multi
selection with the mouse moves instead of starting
> On 24 May 2021, at 15:59, Jason H wrote:
>
>> I have retried with:
>> `./emsdk activate sdk-fastcomp-1.38.27-64bit`
>
>> I'll keep looking into this.
>
> So, It's a bit confusing why fastcomp is mentioned, if it isn't supported?
Ah see, you have to read the fine print:
Cross-posting from the development mailing list in case any of you have a
strong opinion about this.
Volker
> On 28 May 2021, at 13:10, Volker Hilsheimer wrote:
>
> Hey Widget fans,
>
> I need your opinions on https://bugreports.qt.io/browse/QTBUG-59888
>
> The UX resulting from our
This seems unrelated, since the JIRA ticket predates both 5.11 and 5.15, so
while it does sound like a regression that you’re welcome to report, it won’t
help me with deciding about this particular issue.
Cheers,
Volker
> On 28 May 2021, at 15:30, Olivier B.
> wrote:
>
> Here, we have had
Turns out that the patch that fixed QTBUG-1 introduced that behavior
change, and - given that I was the one making that patch - I can say that the
change you are observing is an unintentional side effect.
Created https://bugreports.qt.io/browse/QTBUG-94087 and fix in progress.
Cheers,
I'm trying to make a dashed line in quick3d. I made the line with
QQuick3DGeometry, and exposed it to qml, all good.Then I tried to apply a
custom texture with QQuick3DTextureData, using a texture made with 2 colors
with size of 2x1 pixels, but I only get to see the first color.
I sucessfully
> Ah see, you have to read the fine print: https://doc.qt.io/qt-5/wasm.html is
> the authoritative documentation. I made that clearer on the wiki now;
> apologies for the confusion.
>
> fastcomp (the older fork-of-llvm compiler) is long since history, except if
> you are using an older version
> However I blew away the build dir and did a full rebuild now and got:
> wasm-ld: error: initial memory too small, 21088512 bytes needed
>
> Command line contains: "--initial-memory=16777216 --no-entry
> --global-base=1024"
>
> Progress! :-) How do I change the memory setting [in QtCreator]?
assuming your change "does the right thing in all cases" then i think it should
be the default.
nobody WANTS the currently-bad behavior.
-dave
> On May 28, 2021, at 5:55 AM, Volker Hilsheimer
> wrote:
>
> Cross-posting from the development mailing list in case any of you have a
> strong
14 matches
Mail list logo
