On Wed, Apr 1, 2009 at 9:25 AM, Edward K. Ream <[email protected]> wrote:
> > > On Tue, Mar 31, 2009 at 8:22 AM, Ville M. Vainio <[email protected]>wrote: > >> >> Well, that makes sense. Leo is invoking the idle handler like crazy. > > > Oops. During the sprint I "fixed" the vim plugin by making hooking up the > idle-time code. > > Apparently it needs a bit more work. I'll fix this (at least temporarily) > now. > Is this actually causing problems for you? It's not causing any problems for me. The relevant method is setIdleTimeHook in qtGui.py. It does: # To make your application perform idle processing, use a QTimer with 0 timeout. # More advanced idle processing schemes can be achieved using processEvents(). timer.start(0) The comments are from the Qt docs somewhere (not QTimer). In other words, timer.start(0) is advertised as a special idle-time case, so using it should work. BTW, 100% of the time will always be used by some process. The "system idle" process usually soaks up the slack. The issue is not really whether Leo is using "all" of the cpu cycles; the issue is whether Leo (Qt) is allowing other processes to grab time. I have not seen an actual problem either on Linux or XP. YMMV. If necessary, you can disable setIdleTimeHook. Any other comments or ideas? Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
