Hi,
On Tue, Jun 29, 2010 at 2:58 AM, Thomas Friedrichsmeier
<thomas.friedrichsme...@ruhr-uni-bochum.de> wrote:
> Hi,
>
> On Monday 28 June 2010, Prasenjit Kapat wrote:
>> I haven't tested the new code yet, but is there a 'catch-22' issue
>> here? The dev.off () bug was solved by forcefully closing / killing
>> the window and now the closing itself is mapped to dev.off ()?
>
> well, there is a lot of indirection, but not a full circle, of course.
> Basically the steps are:
> 1) Clicking the close-button (or Window->Close) keeps the window alive, but
> calls dev.off(). This is mandatory, otherwise we wouldn't have a chance to
> record the unsaved plot.
> 2) dev.off(), before calling the internal dev.off(), tells RKWard to close the
> window.
> 3) At this point the window is closed immediately in the GUI thread.
OK, that makes sense now.
> I see. So I'll just turn this into a bug-report, let you deal with it:
> Create a few plots to have a plot history. Close all devices. Open a new
> device. The device is now at the start of the history ("Next plot" is active),
> not at the end ("Prev plot" is not active).
Ah, missed that one totally. Fixed in svn, thanks.
--
Prasenjit
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
RKWard-devel mailing list
RKWard-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkward-devel
