Hi!
I've been facing this irritating behaviour for years now and it's finally time to talk about it.
When directly translating one or more mesh elements (don't worry, in Setup mode 😌), i.e. vertices or edges or groups of them, I sometimes need to perform small and precise tweaks, usually to align one mesh to the other before rigging them to the same skeleton. When this small transformation is too small, Spine automatically and unexplicably deselects the mesh elements I'm working on, going back to the selection of the whole mesh.
Here a video of this behaviour:
I see 3 areas involved in this mechanic, after click&drag has started:
a first safe area of around 5 pixels, in which moving the cursor doesn't produce any change (I guess this is to avoid unintentional transformation while simply clicking)
a second area (where this problem occurs), after the first one, of I think 3 more pixels. Here the object has started moving, but if I stop holding the mouse button, it deselects
the final area in which everything works as expected
I don't get the behaviour of the second area. I think that once the object has started moving, it should simply behave like it does in the third area, so keep the new position and keep the selection. I fact, the second area shouldn't probably even exists, unless I'm missing some other safety measure of some kind.
It might be a bit of an edge case, but believe me it's extremely annoying when you need the precisely position a mesh of many vertexes, and you're trying to make them overlap perfectly 👀
