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
See https://codepen.io/etpinard/pen/brBKdy?editors=0010 where the gl2d_parcoords_1 and gl2d_parcoords_2 mocks are plotted side-by-side. Both newPlot calls are followed by toImage. The top row displays the interactive graphs (i.e. newPlot output) and the bottom row displays the toImage outputs. Now, notice that the gl2d_parcoords_1 image has a few strokes that spilled over from gl2d_parcoords_2.
Fixing this we'll important for the image exporter where multiple parcoords graphs might be exported on the same page at the same time.
See https://codepen.io/etpinard/pen/brBKdy?editors=0010 where the
gl2d_parcoords_1
andgl2d_parcoords_2
mocks are plotted side-by-side. BothnewPlot
calls are followed bytoImage
. The top row displays the interactive graphs (i.e.newPlot
output) and the bottom row displays thetoImage
outputs. Now, notice that thegl2d_parcoords_1
image has a few strokes that spilled over fromgl2d_parcoords_2
.Fixing this we'll important for the image exporter where multiple
parcoords
graphs might be exported on the same page at the same time.cc @monfera
The text was updated successfully, but these errors were encountered: