Re: Rev app 'not responding' under Vista, but fine in XP

2009-10-08 Thread Martin Blackman
Thanks to Richard, Phil  Jacqueline, the 'wait 0' does the trick,
with or without messages. I just put it as the first line in my repeat
loop.
This is what I've found for those who are interested in Vista
behaviour - a stack is more predisposed to become 'not responding' in
the IDE than as a standalone. As a standalone it does not usually
become non-responsive unless there is a lot of other stuff going on;
however if windows task manager is open, my app is almost guaranteed
to become 'non-responsive' during one particular large repeat loop.
However adding a wait 0 at the start of the loop seems to do the trick
(without speed impact), I haven't been able to make it go
non-responsive with that line in there.

regards
Martin
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Rev app 'not responding' under Vista, but fine in XP

2009-10-07 Thread Martin Blackman
Hi folks

Microsoft Vista is classifying my Rev application as 'Not responding'
when it runs a particularly intensive handler. The title bar changes
and screen updates cease. But the program is still working just fine
underneath all that, and once the handler finishes Vista releases the
stranglehold and updates the window.  However users may be
understandably concerned and will not see the progress bar update
normally shown by the program.
This does not happen on XP, it seems that Vista is a little overzealous here.
I believe Rev does its garbage collection after a handler finishes. So
a big repeat loop could instead be changed to repeated calls to a sub
handler.
But I think this would add overhead and besides I'm struggling to
think of a way to modify a couple of my problematic handlers in this
fashion.  Has anyone here had any successful dealings with this issue?

regards
Martin Blackman
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Rev app 'not responding' under Vista, but fine in XP

2009-10-07 Thread Richard Gaskin

Martin Blackman wrote:

Microsoft Vista is classifying my Rev application as 'Not responding'
when it runs a particularly intensive handler. The title bar changes
and screen updates cease. But the program is still working just fine
underneath all that, and once the handler finishes Vista releases the
stranglehold and updates the window.  However users may be
understandably concerned and will not see the progress bar update
normally shown by the program.
This does not happen on XP, it seems that Vista is a little overzealous here.
I believe Rev does its garbage collection after a handler finishes. So
a big repeat loop could instead be changed to repeated calls to a sub
handler.
But I think this would add overhead and besides I'm struggling to
think of a way to modify a couple of my problematic handlers in this
fashion.  Has anyone here had any successful dealings with this issue?


Just a hunch, but I wonder if adding wait 0 with messages would free 
up enough clock cycles to let the OS feel more comfortable.


--
 Richard Gaskin
 Fourth World
 Rev training and consulting: http://www.fourthworld.com
 Webzine for Rev developers: http://www.revjournal.com
 revJournal blog: http://revjournal.com/blog.irv
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Rev app 'not responding' under Vista, but fine in XP

2009-10-07 Thread Phil Davis
I bet the with messages part isn't needed - doesn't that just allow UI 
interaction, which may not be desirable during Martin's process? In 
other words, I don't think it's necessary if you just want to free the 
engine and/or OS to take a breath.


FWIW -
Phil Davis


Richard Gaskin wrote:

Martin Blackman wrote:

Microsoft Vista is classifying my Rev application as 'Not responding'
when it runs a particularly intensive handler. The title bar changes
and screen updates cease. But the program is still working just fine
underneath all that, and once the handler finishes Vista releases the
stranglehold and updates the window.  However users may be
understandably concerned and will not see the progress bar update
normally shown by the program.
This does not happen on XP, it seems that Vista is a little 
overzealous here.

I believe Rev does its garbage collection after a handler finishes. So
a big repeat loop could instead be changed to repeated calls to a sub
handler.
But I think this would add overhead and besides I'm struggling to
think of a way to modify a couple of my problematic handlers in this
fashion.  Has anyone here had any successful dealings with this issue?


Just a hunch, but I wonder if adding wait 0 with messages would free 
up enough clock cycles to let the OS feel more comfortable.


--
 Richard Gaskin
 Fourth World
 Rev training and consulting: http://www.fourthworld.com
 Webzine for Rev developers: http://www.revjournal.com
 revJournal blog: http://revjournal.com/blog.irv


--
Phil Davis

PDS Labs
Professional Software Development
http://pdslabs.net

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Rev app 'not responding' under Vista, but fine in XP

2009-10-07 Thread Richard Gaskin

Phil Davis wrote:

 Richard Gaskin wrote:
 Martin Blackman wrote:
 Microsoft Vista is classifying my Rev application as 'Not
 responding' when it runs a particularly intensive handler.
...
 Just a hunch, but I wonder if adding wait 0 with messages would
 free up enough clock cycles to let the OS feel more comfortable.

 I bet the with messages part isn't needed - doesn't that just
 allow UI interaction, which may not be desirable during Martin's
 process? In other words, I don't think it's necessary if you just
 want to free the engine and/or OS to take a breath.

I had picked up the (mis?)impression that the difference with adding 
with messages is that without it the wait stays in Rev's internal 
even loop, but with it it makes a call to whatever is the current OS 
equivalent of GetNextEvent.


I wouldn't mind being mistaken, though; it's clumsy syntax.

Anyone here know for sure whether the wait command by itself is 
sufficient to free up a call to the OS?


--
 Richard Gaskin
 Fourth World
 Rev training and consulting: http://www.fourthworld.com
 Webzine for Rev developers: http://www.revjournal.com
 revJournal blog: http://revjournal.com/blog.irv

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Rev app 'not responding' under Vista, but fine in XP

2009-10-07 Thread J. Landman Gay

Richard Gaskin wrote:

Phil Davis wrote:

  Richard Gaskin wrote:
  Martin Blackman wrote:
  Microsoft Vista is classifying my Rev application as 'Not
  responding' when it runs a particularly intensive handler.
...
  Just a hunch, but I wonder if adding wait 0 with messages would
  free up enough clock cycles to let the OS feel more comfortable.
 
  I bet the with messages part isn't needed - doesn't that just
  allow UI interaction, which may not be desirable during Martin's
  process? In other words, I don't think it's necessary if you just
  want to free the engine and/or OS to take a breath.

I had picked up the (mis?)impression that the difference with adding 
with messages is that without it the wait stays in Rev's internal 
even loop, but with it it makes a call to whatever is the current OS 
equivalent of GetNextEvent.


I wouldn't mind being mistaken, though; it's clumsy syntax.

Anyone here know for sure whether the wait command by itself is 
sufficient to free up a call to the OS?


It doesn't. Wait with messages does allow a time slice not only for 
the IDE but for background processes as well, but I don't know if it 
also allows garbage collection in the handler.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution