From: Glen Holcomb Date: 2008-07-24T03:43:08+09:00 Subject: Re: Of GUIs threads and scheduling woes ------=_Part_160055_8857880.1216838932057 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, Jul 23, 2008 at 12:21 PM, ara.t.howard wrote: > > On Jul 23, 2008, at 10:36 AM, Glen Holcomb wrote: > > The observed behavior seems to be magnified/caused by minimizing the >> application. Does anyone have any suggestions that could lead to a more >> responsive app? 5+ minutes late wouldn't matter so much if it didn't >> cause >> the thread to miss an event scheduled a minute or two after the one that >> was >> late. I suppose I could re-structure my code and may have to. I was just >> hoping that there is a way to get tolerable responsiveness out of a >> thread. >> > > > > this sounds alot like a process being put to sleep by windows and thereby > causing all threads to sleep - is this on windows? > > a @ http://codeforpeople.com/ > -- > we can deny everything, except that we have the possibility of being > better. simply reflect on that. > h.h. the 14th dalai lama > > > > > Unfortunately it is, which is what I had feared was happening. I'm not sure if being out of focus for a prolonged time has the same effect or not. I was planning on testing that shortly. It would appear there is no way around this and that I will need separate processes. I noticed the mmap library is pretty old, is it reliable? DRb would do what I need but I'd rather do it without opening ports since all the processes would be on the same machine anyway. -- "Hey brother Christian with your high and mighty errand, Your actions speak so loud, I can't hear a word you're saying." -Greg Graffin (Bad Religion) ------=_Part_160055_8857880.1216838932057--