|
From: | Daniel J Sebald |
Subject: | Re: using timers in the GUI |
Date: | Wed, 20 Mar 2013 15:50:28 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 03/20/2013 03:41 PM, Torsten wrote:
On 20.03.2013 17:59, Daniel J Sebald wrote:On 03/20/2013 03:22 AM, John W. Eaton wrote:
[snip]
If there is some reason that these changes can't work, I'd like to understand why. It seems much simpler to call these functions without using timers.Those changes look good. They are pretty much what was discussed as a more event-driven scheme, and use Qt signal/slot as designed. If it seems to run properly, go with it. The timer code will always be in the repository if some issue comes up.Yes, the patches work fine and should also fix bug #38537. Octave now consumes approximately 12% of cpu time on my system with only a few variables in the workspace (without the patch 3..4%). So limiting to one update per prompt would be helpful.
Good test Torsten. You are talking idle time, right? There should be a decrease in CPU time if this becomes event driven, not increase.
Dan
[Prev in Thread] | Current Thread | [Next in Thread] |