similar to: Wayland Display Support in R Plot

Hi I am unaware of any Wayland display support. One useful way forward would be an R package that provides such a device (along the lines of 'Cairo', 'tikzDevice', et al) Paul On 27/10/23 23:16, quentin.thorne via R-devel wrote: > Hello, > > I'm interested in understanding the current state of Wayland display > support in R plot, and I was wondering if any

Hi You could also look at dev.capture(), depending on which screen device you are using. Paul On 16/10/23 05:24, Duncan Murdoch wrote: > On 15/10/2023 12:05 p.m., Shu Fai Cheung wrote: > > Let me clarify my question: > > > > plot.new() > > polygon(c(.5, .5, .75, .8), c(.25, .3, .4, .5)) > > > > If the device is an on-screen device, can I check

On 16.08.2024 13:46, Iago Gin? V?zquez wrote: > Hi all, > > On one hand, I wanted to ask if there is some place where I can check a changelog / NEWS for the grid package, as it is not on CRAN. And in that case, where can I find it? Grid is part of R, hence you can look at R's NEWS, e.g. at <https://cran.r-project.org/doc/manuals/r-devel/NEWS.html> or directly in the svn

Hi Paul Is there a concrete working example somewhere that shows how to use these to do an animation on Windows (R Gui &/or RStudio) using base R plot() and friends? I have several old examples somewhere that used to work (R < ~ 3), but now no longer work as before. Date: Mon, 25 Mar 2024 10:43:29 +1300 From: Paul Murrell <paul at stat.auckland.ac.nz<mailto:paul at

Also see the "arctext" function in the plotrix package. Jim On Fri, Mar 31, 2023 at 11:12?AM Jim Lemon <drjimlemon at gmail.com> wrote: > > Hi Jinsong, > Maybe "srt" will do what you want. As you noted non-orthogonal > rotations may not work on some devices. You may be able to download > mirror fonts from places like fontmirror.com, but it more

Hello: I want to present a sequence of plots as an animation. As a toy example consider the code function(n){for (i in 1:n){ plot(1:100,sin(i*(1:100)),type="l") title(paste("n=",i)) segments(0,0,100,0,col=2) }} This sort-of works on a MacOS platform, but the rendering of the plots is a bit choppy. Inserting a sleep function allows the plots to evolve smoothly.

On 15/10/2023 12:05 p.m., Shu Fai Cheung wrote: > Let me clarify my question: > > plot.new() > polygon(c(.5, .5, .75, .8), c(.25, .3, .4, .5)) > > If the device is an on-screen device, can I check whether a particular area > has anything drawn on it, or, to be precise, whether the color of a > particular area has all pixels equal to the background color. That is, if >

On 3/7/23 13:12, Paul Murrell wrote: > Hi > > I think the main issue here is that you are *drawing* text on the > graphics device, so I would only expect to see literal XML text output > in the result. > ''' > > Hope that helps Thank you for your consideration of the matter, but that seems extraordinarily overly-complicated for the results of

This was actually the first thing that ChatGPT debugged for me. The issue was that I was able to click on the link when I displayed the raw SVG in the browser (you can use that to test whether the syntax is even correct), but not when the svg displays inside a html page with the <img ...> tag. ChatGPT correctly identified the issue and suggested a solution using <object ...> tags

Hi I don't think this is an R issue (it is separate from the Cairo Symbol font problem). For PDF output, R actually relies on the Symbol font having the Adobe Symbol Encoding (Appendix D of the PDF Reference https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/pdfreference1.7old.pdf) and just outputs the font as "Symbol", which relies on it being one of the Standard

I see. Peter, you are right about the font that causes the issue. Paul, thanks for your insights. I'll bring this to the Fedora font experts to see if we can arrive at a more permanent fix. I'll report back with any conclusion. @Martin: Meanwhile, at least you have options. One is to embed the fonts, either as Peter suggested or using cairo_pdf instead. Alternatively, Peter also has shown

> On 30/10/2023, at 8:38 AM, Dirk Eddelbuettel <edd at debian.org> wrote: > > > On 30 October 2023 at 07:54, Paul Murrell wrote: > | I am unaware of any Wayland display support. > | > | One useful way forward would be an R package that provides such a device > | (along the lines of 'Cairo', 'tikzDevice', et al) > > As I understand it, it is

On 29/10/2023 4:20 p.m., Simon Urbanek wrote: > > >> On 30/10/2023, at 8:38 AM, Dirk Eddelbuettel <edd at debian.org> wrote: >> >> >> On 30 October 2023 at 07:54, Paul Murrell wrote: >> | I am unaware of any Wayland display support. >> | >> | One useful way forward would be an R package that provides such a device >> | (along the lines

https://bugs.freedesktop.org/show_bug.cgi?id=109341 Bug ID: 109341 Summary: Plasma Wayland locks up immediately on sign in Product: Mesa Version: 18.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Drivers/DRI/nouveau

On 30 October 2023 at 09:20, Simon Urbanek wrote: | > On 30/10/2023, at 8:38 AM, Dirk Eddelbuettel <edd at debian.org> wrote: | > On 30 October 2023 at 07:54, Paul Murrell wrote: | > | I am unaware of any Wayland display support. | > | | > | One useful way forward would be an R package that provides such a device | > | (along the lines of 'Cairo',

El lun., 30 oct. 2023 12:26, Roger Bivand <Roger.Bivand at nhh.no> escribi?: > I also noticed this: > > https://www.theregister.com/2023/10/13/gnome_proposes_dropping_x11/ > > which is concerning. Until now, I've retained X11 on Fedora because of > difficulties in screen sharing via zoom in Wayland sessions. > KDE Plasma user here. FWIW, I've been using Wayland

On 30 October 2023 at 07:54, Paul Murrell wrote: | I am unaware of any Wayland display support. | | One useful way forward would be an R package that provides such a device | (along the lines of 'Cairo', 'tikzDevice', et al) As I understand it, it is a protocol, and not a device. Several Linux distributions have long defaulted to it, so we already should have thousands of

Hi The general "evolution" of grid.*() functions (that I have written) have tended towards the grid.polyline() style ... grid.*(...) { grid.draw(*Grob(...)) } With my thinking at least heading towards: if you are calling grid.*(), then you want to actually draw something; if you want to just create a description of something to draw, then you want to call *Grob(). In other

https://bugs.freedesktop.org/show_bug.cgi?id=48074 Bug #: 48074 Summary: 3D / OpenGL clients used with wayland always cause an immediate hang Classification: Unclassified Product: Mesa Version: 8.0 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium

I also noticed this: https://www.theregister.com/2023/10/13/gnome_proposes_dropping_x11/ which is concerning. Until now, I've retained X11 on Fedora because of difficulties in screen sharing via zoom in Wayland sessions. Roger -- Roger Bivand Emeritus Professor Norwegian School of Economics Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway Roger.Bivand at nhh.no