Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Behaviour of the plotting pane #2738

Open
3 tasks
Tracked by #4734
thomasp85 opened this issue Apr 11, 2024 · 2 comments
Open
3 tasks
Tracked by #4734

Behaviour of the plotting pane #2738

thomasp85 opened this issue Apr 11, 2024 · 2 comments

Comments

@thomasp85
Copy link

This issue serves as a list of observations about how the plotting pane differs from the normal expectations of an R graphics device (in the sense that these should get fixed to bring it in line with expectations)

  • grid::new.page()/plot.new() should open a blank plot. Currently, calling these will not produce any discernible result. Only further plotting operations will show that a new plot was created.
  • Calling grid::grid.points(1:10, 1:10) (or something to that effect) after having cleared all plots from the plotting pane does not have an effect. If no graphic device is available, a new default one should be opened (as it happens when calling the above in a fresh positron session)
  • The plotting pane does not process any events and locator() doesn't work since it is a shim over png(). It would be expected that an on-screen device had this capability
@kevinushey
Copy link
Contributor

How important do you think it is that Positron supports the locator out of the box?

Are there some examples of plot events (or how those plot events are used) that we could use as an example? Is there a set of these that you feel are essential to support?

@thomasp85
Copy link
Author

Of the three, the event/locator part is def the lowest priority, but it will trip up those that use it. Biggest use case in my world I know of is the directlabels package but I'm sure it is essential to someones workflow :-)

@juliasilge juliasilge added this to the Future milestone Apr 16, 2024
@DavisVaughan DavisVaughan mentioned this issue Sep 18, 2024
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants