Robert,

  Thanks for the explanation.  Just for more info, it looks like the Aug
30 build has the same issue on my Win2k pro system.

  Based on your description and on examination of the behavior that I
can see here, it looks like when the mouse isn't moving the update still
does some work behind the scenes to a point and then halts until I can
move the mouse. Because when I do move the mouse there is a quick jump
to a point then things resume.  It's as if a small buffer is being
filled up until the mouse is moved.
  It looks like some idle cycles get stolen from other processes unless
there's activity in the plucker desktop window, such as moving the
mouse. (or maybe more accurately, idle cycles aren't reported to the
window accurately unless there's some activity there.)

 Don't know if any of this helps, but that's about all I can tell you.


On Tue, 2002-09-10 at 12:16, Robert O'Connor wrote:
> > I may have missed someone else posting this... but has anyone else had
> > the funky issue for the windows plucker desktop where the progress bar
> > (and progress in general) does not move unless you move the mouse around
> > within the plucker desktop window?
> > 
> > I know it sounds bizarre, but it's true (on my system, at least). When
> > updating a channel, the progress halts until I move the mouse and then
> > the progress bar jumps a little.  This means that my scheduled
> > (unattended) updates don't do a whole lot until I come back and move my
> > mouse around and watch it update...
> > 
> >  For info, I'm running Win2k pro with the 7/16/02 posted plucker
> > desktop.
> 
> Hi, thanks for your feedback. 
> 
> This is not a known issue. If it gets reported by anyone else, will have a closer 
>look. 
> 
> Most likely the reason is that you are using a version from 7/16/02 and the progress 
>dialog 
> code was rewritten again from scratch in August. This changes the progress dialog 
> implementation as well as a lot of other changes.
> The newer downloads are available from:
> http://desktop.plkr.org
> 
> The way updating is implemented:
> -On an idle event (that is, the processor has a chance to breathe and do something):
> ------While there is any output text from the parser:
> ----------Put the output text into the listbox and move the gauges.
> 
> 
> Best wishes,
> Robert
> _______________________________________________
> plucker-list mailing list
> [EMAIL PROTECTED]
> http://lists.rubberchicken.org/mailman/listinfo/plucker-list
> 


_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list

Reply via email to