Em quarta-feira, 8 de março de 2017, às 21:09:49 CET, Jake Petroules escreveu:
> Right now we depend on JSC via QtScript (not V4) but that will change at
> some point. We're not entirely sure of the solution yet; newer JSC vs V8 vs
> V4 or another solution.
Have you tried the JerryScript interpret
Hello,
I am trying to disable Qt auto-scrolling on mobile devices(iOS, Android) when
focusing on an input field in QtQuick.
For iOS it was pretty simple and just for a proof of concept making
QIOSInputContext::scrollableRootView to always to return 0 disabled the
auto-scrolling so we can in our
> On Mar 8, 2017, at 12:15 PM, Sune Vuorela wrote:
>
> On 2017-03-08, Jake Petroules wrote:
>> I'm working on the qbs bootstrapping. The requirements will be: a C++11 com=
>> piler. End of requirements. Seriously. Not even bash, if you don't mind typ=
>> ing a couple commands manually.
>
> I d
On 2017-03-08, Jake Petroules wrote:
> I'm working on the qbs bootstrapping. The requirements will be: a C++11 com=
> piler. End of requirements. Seriously. Not even bash, if you don't mind typ=
> ing a couple commands manually.
I don't mind a bat script, a bash script or whatever is needed, but
I'm working on the qbs bootstrapping. The requirements will be: a C++11
compiler. End of requirements. Seriously. Not even bash, if you don't mind
typing a couple commands manually.
Right now we depend on JSC via QtScript (not V4) but that will change at some
point. We're not entirely sure of t
On 2017-03-07, Lars Knoll wrote:
> This also makes qbs a natural choice to also use for Qt itself, and I belie=
> ve all the people that have worked and maintained Qt's build system over th=
> e last few years are supporting this. Of course this requires that we can s=
> how that qbs can be used t
On Tue, Mar 07, 2017 at 11:46:58AM +0100, Thiago Macieira wrote:
> Em terça-feira, 7 de março de 2017, às 08:16:14 CET, Simon Hausmann escreveu:
> > I for one would welcome a C++ rewrite of syncqt inside qmake to get rid of
> > the perl dependency. However I do not have the authority to approve suc
Em quarta-feira, 8 de março de 2017, às 14:44:51 CET, Ulf Hermann escreveu:
> > That said, look at the numbers: it increased from ~100 µs to 16.9 ms in
> > the
> > worst case. You can't perceive that difference.
>
> This limits the number of processes you can spawn per second to about 60
> (and it
That said, look at the numbers: it increased from ~100 µs to 16.9 ms in the
worst case. You can't perceive that difference.
This limits the number of processes you can spawn per second to about 60
(and it goes lower if you eat more RAM). I certainly can notice this
when using the version of qb
Em quarta-feira, 8 de março de 2017, às 13:51:49 CET, Christian Kandeler
escreveu:
> I use the default settings for overcommit (0/heuristic). My application
> starts QProcesses in a loop. If the application has not allocated
> additional memory, strace -T for clone() gives:
>
> <0.79>
> <0.00
On 03/07/2017 10:05 PM, Thiago Macieira wrote:
> Em terça-feira, 7 de março de 2017, às 17:53:41 CET, René J.V. Bertin
> escreveu:
>> One tends to forget (I do at least) that spawning a little helper process
>> can be quite expensive, sometimes prohibitively so. Makes you wonder what
>> kind of cr
Em quarta-feira, 8 de março de 2017, às 11:37:43 CET, Kai Koehne escreveu:
> I take the blame for not preparing the session properly then. Anyhow, it was
> never intended as a decision forum in the first place.
It couldn't have been. Only this mailing list is allowed to make decisions for
the Qt
Em quarta-feira, 8 de março de 2017, às 12:55:58 CET, Sérgio Martins escreveu:
> On Wed, Mar 8, 2017 at 11:33 AM, Alex Blasche
wrote:
> > This is an ancient thread but just to keep this in mind (it certainly cost
> > me a day re-figuring this out).
> >
> > If you do Qt development for Android yo
On 9 March 2017 at 00:33, Alex Blasche wrote:
> This is an ancient thread but just to keep this in mind (it certainly cost me
> a day re-figuring this out).
>
> If you do Qt development for Android you are going to be hit by this. The
> four most recent Android NDKs (11c, 12b, 13b & 14) are affe
On Wed, Mar 8, 2017 at 11:33 AM, Alex Blasche wrote:
> This is an ancient thread but just to keep this in mind (it certainly cost me
> a day re-figuring this out).
>
> If you do Qt development for Android you are going to be hit by this. The
> four most recent Android NDKs (11c, 12b, 13b & 14) a
This is an ancient thread but just to keep this in mind (it certainly cost me a
day re-figuring this out).
If you do Qt development for Android you are going to be hit by this. The four
most recent Android NDKs (11c, 12b, 13b & 14) are affected by this bug when
using Linux (not all Linux distro
On 8 March 2017 at 10:37, Kai Koehne wrote:
> > -Original Message-
> > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> > project.org] On Behalf Of Richard Moore
> > Sent: Tuesday, March 07, 2017 10:44 PM
> > To: Lars Knoll
> > Cc: Thiago Macieira ; Qt development mai
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Richard Moore
> Sent: Tuesday, March 07, 2017 10:44 PM
> To: Lars Knoll
> Cc: Thiago Macieira ; Qt development mailing
> list
> Subject: Re: [Development] syncqt.pl in C++
André Somers (8 March 2017 06:18)
> The stopping maintainance of qmake can't happen any time soon I'd
> think. Not even from Qt6. There are too many Qt projects out there
> depending on it.
All the same, the sooner we can make the transition away from using it
ourselves, the sooner we can retire q
19 matches
Mail list logo