Very cool, thanks for the tip. And good luck with the difficulty inherent in
that feature.
> On Feb 10, 2017, at 8:49 PM, Jake Petroules wrote:
>
> While we can't officially promise anything for any particular timeframe...
> see http://blog.qt.io/blog/2017/02/06/native-look-feel/
>
>> On Feb
While we can't officially promise anything for any particular timeframe... see
http://blog.qt.io/blog/2017/02/06/native-look-feel/
> On Feb 10, 2017, at 6:33 PM, Patrick Stinson wrote:
>
> Hello! What is the status for supporting native iOS gui elements in Qt? Or
> are most people just buildin
Hello! What is the status for supporting native iOS gui elements in Qt? Or are
most people just building apps from scratch with their own custom widgets. I
mean, using a basic Qt scroll view for example is not really acceptable in an
iOS app but the native iOS scrollbars are.
Along the same lin
Hi,
I think I have found a behaviorial change in Qt 5.8 (compared to Qt5.7.1),
but I am not sure which part is causing this.
If I run the sample code (the second one from the website [1]), it spreads
nicely when it's compiled with Qt 5.7.1. If I compile the same code with Qt
5.8, it doesn't sprea
Em sexta-feira, 10 de fevereiro de 2017, às 16:27:49 PST, Etienne Sandré-
Chardonnal escreveu:
> Thanks for the link. Yes, I'm doing something bad, but there is no strong
> reason to encode a string litteral differently than a QByteArray and not
> allowing this. But since retro-compatibility is mor
> On Feb 10, 2017, at 9:27 AM, Etienne Sandré-Chardonnal
> wrote:
>
> Thanks for the link. Yes, I'm doing something bad, but there is no strong
> reason to encode a string litteral differently than a QByteArray and not
> allowing this. But since retro-compatibility is more important I suppose
There is also something new here https://codereview.qt-project.org/#/c/178543/
WIP: Introduce mkspec for web assembly
Regards,
Gunnar Roth
Gesendet: Freitag, 10. Februar 2017 um 09:44 Uhr
Von: "Viktor Engelmann"
An: interest@qt-project.org
Betreff: Re: [Interest] Qt in browser with emscr
I think it's str.c_str() that's adding the null character at the end of
your string, not anything with QDatastream or QBytearray.
On Fri, Feb 10, 2017 at 9:27 AM, Etienne Sandré-Chardonnal <
etienne.san...@m4x.org> wrote:
> Thanks for the link. Yes, I'm doing something bad, but there is no strong
Thanks for the link. Yes, I'm doing something bad, but there is no strong
reason to encode a string litteral differently than a QByteArray and not
allowing this. But since retro-compatibility is more important I suppose
this cannot be changed...
Is there a page summarizing all QDataStream >> overl
> -Original Message-
> From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org]
> On Behalf Of Jani Tykka
> Sent: Friday, February 10, 2017 2:45 PM
> To: interest@qt-project.org Interest
> Subject: [Interest] QML WebEngineView and CPU usage
>
> Hi,
>
> It seems that QML W
I was not comparing directly, but through a QSet, which was
initially populated using string litterals. So I inserted "test" but after
reading from the stream I had "test\0"
2017-02-09 22:00 GMT+01:00 Mike Chinander :
> How are you comparing it to "test" after reading to the QByteArray? You
> cou
Hi,
It seems that QML WebEngineView is quite beast in eating CPU. I think
the cause for this is Chromium behind the WebEngine not yielding CPU
cycles? Is there any suggestions available how to improve the
situation?
Thanks,
Jani
--
This email is intended solely for the person or entity to whi
At Qt World Summit 2015, Morten Sørvig did a presentation about Qt in
NaCl, where he also
addressed emscripten. On
https://www.qt.io/resource-center-qtws15-session-listing/
you find the link to YouTube: https://www.youtube.com/watch?v=ugkaC6yIG2w
Finding that link on qt.io was MUCH harder than it s
13 matches
Mail list logo
