Hi,
On Saturday 19 June 2010, Prasenjit Kapat wrote:
> Looking at Deepayan's reply:
> http://article.gmane.org/gmane.comp.lang.r.debian/1268
>
> i think it might be "easy" to implement the history part (paginated
> device may be more difficult) for our graphics device.
>
> The idea would be to s
HI,
On Saturday 19 June 2010, Prasenjit Kapat wrote:
> Now, (i) can be broken down into three completely separate plugins:
> (i.1) Context menu for an open data.frame
> (i.2) Context menu for selected object from the workspace browser (w/o
> opening it in data.frame editor)
> (i.3) Edit menu.
>
>
On Sun, Jun 20, 2010 at 9:22 AM, Thomas Friedrichsmeier
wrote:
> Hi,
>
> On Saturday 19 June 2010, Prasenjit Kapat wrote:
>> Looking at Deepayan's reply:
>> http://article.gmane.org/gmane.comp.lang.r.debian/1268
>>
>> i think it might be "easy" to implement the history part (paginated
>> device ma
On Sunday 20 June 2010, Prasenjit Kapat wrote:
> OK. I see the problem now. I have two questions: Is it possible for
> rkward to know
>
> 1. when/if the current device is altered? For example, suppose abline
> () is called after a plot() call, does rkward know the device has been
> modified? My gu
Calling dev.off() creates a new cairo device instead of closing the
existing one:
> plot (1,1)
> dev.off()
Warning message:
In dev.off() : Display list redraw incomplete
X11cairo
4
Now, calling dev.off() twice closes the two devices.
> dev.off()
X11cairo
3
> dev.off()
null device
Hi,
On Sun, Jun 20, 2010 at 7:46 PM, Thomas Friedrichsmeier
wrote:
> On Sunday 20 June 2010, Prasenjit Kapat wrote:
>
>> 2. when/if the graphics window is closed? I can handle dev.off () and
>> graphics.off() but what happens if the close button on the window is
>> clicked? Or Window > Close (Ctl
