The latter only copies the current state of the markup, not what’s saved.
It’s not random, it’s <3dm file name>_<markup name>.jpg , Keep in mind you can multi select few markups and export them at the same time with this naming convention. It’ll be inconvenient to pop up a dialog asking for a name for each one.
I presume that the forward/backward leafing functionality at the right top is supposed to restore the view used in the Markup? This does not seem to work always. (But maybe those Markups are from an earlier version, so that’s why the view is not restored.)
Now the million dollar question: Does it also restore active clipping planes? And does it restore the Layer state ? If not, then you need to add that …
And does it restore the active Cplane for the Markup? And the “Project to Cplane” snap ?
And could you briefly explain were the Markup is stored? Because it seems to land in Layers used in the files. Meaning that if those Layers are off, then there will be no Markup visible ? Or is this a misunderstanding of the functionality?
What I mean is that in other views, the operation axis can be seen. Use the operation axis and perform a series of command operations (such as stretching, proportional scaling, etc.) It is not a curve or a line
That’s a workaround for now.
The system should be foolproof.
Good it’s on tune-up list.
When a viewport is intentionally locked, then it gets unlocked.
That can’t be wanted. The viewport lock for Markup must not interfere with the normal viewport lock.