octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems with plotting (Windows)


From: Michael Goffioul
Subject: Re: Problems with plotting (Windows)
Date: Sat, 10 Feb 2007 16:57:19 +0100
User-agent: Thunderbird 1.5.0.9 (Windows/20061207)

John W. Eaton a écrit :
On 10-Feb-2007, Michael Goffioul wrote:

| I detected 2 problems in the new plotting system:
| - drawnow.m: use "dumb" terminal is DISPLAY variable is not defined;
| under Windows, this variable is not defined, so adding a "&& isunix()" in
| the test would be OK
| - __uiobject_delete__.m: closing the plot stream is not preceeded by a
| "quit" statement, to close gnuplot properly; this makes the pclose statement
| to hang indefinitely.

OK, I checked in the following changes.  Does this help?

Yes, thanks. Howerer, I notice 2 other problems:
1) with the patch you sent, figures (and gnuplot) can now be closed properly when you explicitely call "close". The problem still exists when I exit octave while a figure is open: it hangs (maybe this problem only occurs under Windows; if required, I can try to debug it to see where it hangs, but in this case I have to recompile everything) 2) some files use "mlock()", especially "get.m". This is a problem when I switch to another plotting system like octplot, which also includes such function. If I switch after "get.m" has been executed at least once (for instance by plotting something), then octplot is unable to overload it (by prepending its own path to the load paths), because the file is locked. You then end up with octplot calling "get.m" from
gnuplot-based plotting system.

Michael.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]