Gentlemen,
I've observed a suspected bug in R-3.60 for Windows 10.
I am using the latest R version, but I have observed the same error in all
releases: alpha, beta RC and released.
Also the same issue occurs in the 32 and 64 bit GUI versions. The program
header I invoke is:
R version 3.6
On 27/04/2019 10:30 a.m., Len Weil wrote:
Gentlemen,
I've observed a suspected bug in R-3.60 for Windows 10.
I am using the latest R version, but I have observed the same error in all
releases: alpha, beta RC and released.
Also the same issue occurs in the 32 and 64 bit GUI versions. The
On 27/04/2019 2:46 p.m., Duncan Murdoch wrote:
On 27/04/2019 10:30 a.m., Len Weil wrote:
Gentlemen,
I've observed a suspected bug in R-3.60 for Windows 10.
I am using the latest R version, but I have observed the same error in all
releases: alpha, beta RC and released.
Also the same iss
I had a look at the current code, and AFAICT it has essentially the same
structure as it did back then. I think it may have finally dawned upon me what
the issue really is:
The logic is that in Rf_addX11Device, we have
if (!X11DeviceDriver(dev, display, width, height,
