Re: [Visualpython-users] gdisplay objects seldom work

[Gary P. <pa...@in...>]

----- Original Message ----- 
From: "Joe Heafner" <hea...@vn...>



> Hi.
>
> I'm running Mac OS X (10.2.6) and Visual 2.1.1 compiled from source.

ditto, except I have 2.1.somethingelse

> I'm still experiencing problems with gdisplay objects. If I create, for
> example, a graph with gcurve the program usually stalls upon execution,
> but no errors are indicated. Sometimes, roughly 90% of the time, both
> the main window and the graph window open up but the graph window is
> just blank and the other window, usually containing an animation of a
> physical system (e.g. oscillating spring-mass system) remains static.
> Sometimes, roughly 10% of the time, the graph shows up correctly, but
> NOT point by point. The entire graph is displayed after the animation
> is over, and the oscillating spring-mass never appears to move at all.
> On a very, very few occasions I get the correct output, which is an
> oscillating spring-mass system in one window and a graph updated in
> real time in the other window. However, I never ever get the program to
> work completely correctly twice in a row. Everything works fine when
> all the gdisplay related statements are commented out.

In my case the program never locks up, but it does stutter a bit, especially
when the animation first starts.  And I have seen the stutter be long enough
that the simulation is all but finished before the graphics start, and then
they're there all at once (as you described).   I've experimented with
placing a time.sleep(n) [where n is typically between 2 and 7]  at various
places.  I find that if I initialize the gdisplay window,  then
time.sleep(),  then start my "while" loop,  I don't lose any of the
animation.  Of course, there is a bit of a delay, and it's still a bit
jerky, but it works.  YMMV.

>
> Another issue is that when a program that uses a gdisplay object
> terminates, the only way to remove the open windows is to choose "End
> program" from inside IDLE. Otherwise, the output windows remain active
> and can only be removed by opening up an xterm, issuing "top", getting
> the PID, exiting "top", and issuing "kill xxx" where xxx is the pid of
> the correct python22 process.

Yep.  But simply restarting the program (F5) kills the old windows and opens
new ones. At the end of the day, though, its "End Program".  Would "ps" be a
hair more convenient than "top"?

-gary

>
> Any ideas what's going on?
>
> Cheers,
> Joe Heafner
>
> -----
> New email address: hea...@ct...
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Visualpython-users mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users