Re: [Visualpython-users] gdisplay objects seldom work

[Bruce S. <bas...@un...>]

Jonathan Brandmeyer explained to me that there is a fundamental problem 
with which I was unaware. Recent versions of the Unix/Linux kernel no 
longer do "recursive" locking/unlocking of resources, something that 
Visual has used. Jonathan has been working on eliminating the deadlocks 
that can now occur and which may well be responsible for what you're 
seeing. He's doing this in his experimental Boost-based version but 
might retrofit the current Visual. This is not a problem on Windows.

Bruce Sherwood

Joe Heafner wrote:

> Hi.
>
> I'm running Mac OS X (10.2.6) and Visual 2.1.1 compiled from source. 
> 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.
>
> 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.
>
> 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