Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Thiago Macieira
On Wednesday, 30 August 2017 17:17:32 PDT René J. V. Bertin wrote: > Thiago Macieira wrote: > > It makes QTimer possible. > > That sounds quite important to me :-) > > I guess so :) I still don't get what purpose calling QObject::timerEvent() > has if the method itself does nothing. Gives me

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread René J . V . Bertin
Thiago Macieira wrote: > It makes QTimer possible. .. > That sounds quite important to me :-) I guess so :) I still don't get what purpose calling QObject::timerEvent() has if the method itself does nothing. Gives me something to ponder. > function, because it would break the existing code.

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Thiago Macieira
On Wednesday, 30 August 2017 14:17:05 PDT René J. V. Bertin wrote: > Thiago Macieira wrote: > > Oops, missed this one. > > > Unfortunately, we can't change anymore. > > Can someone explain what could possibly be broken by changing this? Can the > current base-level QObject::timerEvent() be used

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread René J . V . Bertin
Thiago Macieira wrote: Oops, missed this one. > Unfortunately, we can't change anymore. Can someone explain what could possibly be broken by changing this? Can the current base-level QObject::timerEvent() be used for anything constructive other than heating the office or preventing a CPU

[Development] Backporting the Keccak change

2017-08-30 Thread Thiago Macieira
When writing the 5.6.3 changelog, I'm currently leaving it with: ** * Important Behavior Changes *

[Development] NSMenu validation, QCocoaMenu and button (context etc) menus

2017-08-30 Thread René J . V . Bertin
Hi, I ran into and reported a CPU burning issue a couple of days back, which was quickly resolved. It intrigued me why an application that doesn't use native Mac menus at all would be calling [NSMenu update] at all. I now know that the menu which triggered the scheduled NSMenu update is one

Re: [Development] Qt and IoT infographic

2017-08-30 Thread Thiago Macieira
On Wednesday, 30 August 2017 07:32:42 PDT Jason H wrote: > > For one-offs or maybe tens of copies, sure, there's a lot of Arduinos. And > > a lot of Raspberry Pis too. > > > > For production runs, that number goes very quickly to zero. > > I guess this comes down to whom you are marketing. I can

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Thiago Macieira
On Wednesday, 30 August 2017 00:30:05 PDT Olivier Goffart wrote: > We can change the documentation and recommend against using killTimer and > startTimer. QBasicTimer should be used instead. This would have probably > avoided the problem in this case (as one would have called stop instead of >

Re: [Development] Qt and IoT infographic

2017-08-30 Thread Jason H
> Sent: Tuesday, August 29, 2017 at 5:07 PM > From: "Thiago Macieira" > To: development@qt-project.org > Subject: Re: [Development] Qt and IoT infographic ... > > Besides, this comes a bit as disdainful. I work in music research and > > *everything* embedded uses

[Development] Qt 5.9.2 snapshot available

2017-08-30 Thread Jani Heikkinen
Hi, We have new Qt 5.9.2 snapshot available via online installer. Instructions how to get it here: https://wiki.qt.io/How_to_get_snapshot_via_online_installer Snapshot is based on https://codereview.qt-project.org/#/c/203493/ Packages are smoke tested and seems to be OK so please take a tour.

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Jean-Michaël Celerier
> Today, that QObject::schedule is achieved by (ab)using QTimer::singleShot(0, func). There have been interesting discussions on StackOverflow about this : https://stackoverflow.com/questions/21646467/how-to-execute-a-functor-or-a-lambda-in-a-given-thread-in-qt-gcd-style

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Giuseppe D'Angelo
Il 30/08/2017 11:28, Morten Sørvig ha scritto: There is also the option of creating new API that better covers the use case of running a pice of code once when control returns to the event loop. In use this could look something like this: QCocoaMenu::scheduleUpdate() { if

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Morten Sørvig
> On 30 Aug 2017, at 09:30, Olivier Goffart wrote: > > Am Dienstag, 29. August 2017, 17:30:56 CEST schrieb Thiago Macieira: >> On Tuesday, 29 August 2017 01:10:53 PDT René J.V. Bertin wrote: >>> Which we just rediscovered :) Funny though, apparently 1 misdirected >>>

Re: [Development] Qt and IoT infographic

2017-08-30 Thread Shawn Rutledge
> On 29 Aug 2017, at 18:00, Thiago Macieira wrote: > > On Tuesday, 29 August 2017 02:43:44 PDT Shawn Rutledge wrote: >> And yet it has a web server for serving up either a human-readable page or >> JSON on demand, and it also pushes data to a central server

Re: [Development] Qt and IoT infographic

2017-08-30 Thread Edward Welbourne
Thiago Macieira (earlier): >>> Research shows NO ONE deploys Arduino for real products. It's a >>> maker toy, stuff hobbyists use to make one-off things and some >>> professional makers use for initial prototyping. When they get >>> serious, Arduino goes out the window and they get real boards.

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Philippe
Maybe even deprecate startTimer and killTimer? -1 I like this low level insight, which gives me a higher sense of control about what's going on. Philippe On Wed, 30 Aug 2017 08:06:35 + Lars Knoll wrote: >> On 30 Aug 2017, at 09:30, Olivier Goffart

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Lars Knoll
On 30 Aug 2017, at 09:30, Olivier Goffart > wrote: Am Dienstag, 29. August 2017, 17:30:56 CEST schrieb Thiago Macieira: On Tuesday, 29 August 2017 01:10:53 PDT René J.V. Bertin wrote: Which we just rediscovered :) Funny though, apparently 1

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

2017-08-30 Thread Olivier Goffart
Am Dienstag, 29. August 2017, 17:30:56 CEST schrieb Thiago Macieira: > On Tuesday, 29 August 2017 01:10:53 PDT René J.V. Bertin wrote: > > Which we just rediscovered :) Funny though, apparently 1 misdirected > > startTimer() call can turn any application in a CPU hog that burns cycles > > without