You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is different from new graphics engine features #174 in that this issue can be resolved by providing stubs that do nothing instead of actually supporting the new graphics features (although the latter would be great!)
When closing enhanced 'dev.capabilities()' support #152 (thanks!) I think deviceVersion was set to 15 (in order to support the capabilities() device callback) and thus I speculate that is why R expects that the these callbacks exist and these crashes are occurring because they don't. I speculate that if these device callbacks were provided (even if just stubs that did nothing) these crashes may stop occurring.
The new graphics engine version requires that the graphics device provides the following new device callbacks:
defineGroup()
useGroup()
releaseGroup()
stroke()
fill()
fillStroke()
capabilities()
In each case, it is possible to provide a stub that does nothing. The graphics engine will call the device, but there will just be no output produced.
The postscript() graphics device provides a template for this approach. A graphics device package can model its device callbacks on functions like PS_defineGroup() in devPS.c.
The text was updated successfully, but these errors were encountered:
{svglite}
and observing freezes/crashes to their R systemsdeviceVersion
was set to 15 (in order to support thecapabilities()
device callback) and thus I speculate that is why R expects that the these callbacks exist and these crashes are occurring because they don't. I speculate that if these device callbacks were provided (even if just stubs that did nothing) these crashes may stop occurring.defineGroup()
useGroup()
releaseGroup()
stroke()
fill()
fillStroke()
capabilities()
The text was updated successfully, but these errors were encountered: