> JJ Allaire
> on Sun, 14 Jun 2015 07:41:53 -0400 writes:
>> I have neither been involved in the creation of the
>> 'noRStudioGD' option, but from looking at dev.new() it is
>> clear that it *should* work on all three platforms
>> (Windows, Mac, Linuxen).
>>
>
On Sun, Jun 14, 2015 at 3:46 PM, Alex Chubaty wrote:
> JJ, do you have an estimated timeframe for when this fix will appear?
> There's still the issue of RStudio users not updating their software at each
> and every release, so it may time some time for `dev.new` to work for most
> people.
This i
Thank you Martin for passing this along to RStudio, and thank you JJ for
your reply.
JJ, do you have an estimated timeframe for when this fix will appear?
There's still the issue of RStudio users not updating their software at
each and every release, so it may time some time for `dev.new` to work
> I have neither been involved in the creation of the
> 'noRStudioGD' option, but from looking at dev.new() it is clear
> that it *should* work on all three platforms (Windows, Mac,
> Linuxen).
>
> It is really unfortunate that this still does not work reliably
> (or stopped working with a new rel
> Alex Chubaty
> on Fri, 12 Jun 2015 14:41:56 -0700 writes:
> Dear list members,
> Use of platform-specific code to open new plot devices (e.g., `quartz`,
> `x11`) is discouraged in favour of using `dev.new`; however, this does not
> work in RStudio. A purported soluti
Dear list members,
Use of platform-specific code to open new plot devices (e.g., `quartz`,
`x11`) is discouraged in favour of using `dev.new`; however, this does not
work in RStudio. A purported solution introduced in R 3.1.1 was to call
`dev.new(noRStudioGD = TRUE)`, which works on Windows, but n
