What inspired this wish list request?
(edit) Apparently the template drops a bunch of text here. The inspiration is that selected rows are drawn above EVERY custom user-generated graphics script, regardless of the draw order given.
I understand that the devs were trying to fix the issue of un-selected data points being drawn above selected data points, but they took the lazy fix and just clobbered any hope of having the user determine the draw order. Now selected points are drawn above everything else. I'm almost surprised that the mouse is drawn above selected data points.
What is the improvement you would like to see?
(edit as this form dropped my previous response) I would like to see JMP adhere to the draw order given in the graph customizations list. If a users attaches a graphics script AFTER the marker seg, then any elements drawn by that script should be drawn on top of all markers, Period. End of story.
Why is this idea important?
(edit, as this form dropped my first response) This is clearly important. Extremely important. To the point that my org is putting serious resources into alternatives such as Python or online with JS. There is a large number of work-flows that now cannot be done in JMP14 or 16, full stop.
Consider this graph:
Here I might want to highlight a specific item by selecting it in the legend. When I do, the dense data points completely obscure EVERY SPLINE, even though the splines are drawn as separate scripts AFTER the marker segs.
This is just one example. In my org it is common to have many thousands or even hundreds of thousands of data points. Drawing some sort of custom summary graphic above the data points (whether it's splines, goal lines, confidence intervals, or any other such custom graphic) is needed for properly consuming the data. With JMP14 and beyond, this becomes totally useless for interactivity, since selecting items (and the associated data points) completely obscures EVERY and ALL other graphics drawn on the graph.
And while my org is slow to update to new JMP versions (as many are still using JMP12), I'm left telling people that it's impossible with the new versions of JMP to have the same workflow as before. Instead of being faster with better features, we're left with something completely useless.
And while I do understand that a user can simply deselect the rows (say by clicking a single data point), this type of work-around to a fundamentally bad design decision by the JMP devs should not be necessary, and is not always acceptable (and also changes the visual story / significance):
From my perspective this is so egregiously bad that JMP should provide a hot-fix and patch all users systems in JMP14 and beyond, not wait till JMP18 to fix.
... View more