• Editor
  • Fine Tuning Suggestion

First off, let me just say that Spine has improved leaps and bounds over the past year, and I can't thank the dev team enough for their dedication to making it the best it can be! Every new feature seems to make my life easier, and I know how easily the opposite could be true, so it's a testament to how much you listen to the community and to your careful versioning and testing.

That in mind, I thought I would share a very small suggestion, since every little bit helps Spine shine. When using manipulators involving large scales while zoomed in, I often find that I have trouble dialing in a specific position/rotation/scale through mouse movement alone, and usually resort to testing and revising numbers in the transform fields until I arrive at the ideal placement.

In Maya, where one often has objects of disparate scale in a scene and the manipulator occasionally struggles to adapt on the fly to the scale at which it believes you're currently trying to work, you can hold down the Ctrl key during any transformation operation to greatly increase the mouse input sensitivity. Instead of a 0.01 value change requiring only one pixel of mouse movement, it may require ten pixels in this mode, for instance.

It may just be owing to the fine resolution of my screen that I run into this issue as often as I do, but any sort of modifier key to temporarily increase sensitivity in this way seems like it would be consistently useful, if the implementation of such a thing wouldn't present undue difficulty. As it stands, pressing Ctrl during an operation appears to freeze it in place, but neither Alt nor Shift seem to do anything, so perhaps they're fair game, or some combination thereof.

While testing just now, I also noticed that I am able to set an object's transform to discrete positions via mouse input that can't seem to be arrived at using numerical input (due to rounding to the second decimal there), which adds further potential value to an increased sensitivity mode for those extra fine detail moments.

And here's the part where someone informs me that this already exists, hah! 😉

Related Discussions
...
  • Düzenlendi

Thank you for the kind words! :heart:

Ideally Spine handles this without the need to use modifiers. Can you give an example where it is difficult to manipulate something when zoomed in? You could use one of the example projects or post a project (with or without images) if necessary.

Note you can drag up/down on the transform text fields to adjust them, and shift while dragging gives you finer movement. The same is true for using your mouse wheel while hovering over a field, and shift + mouse wheel. These adjustments don't scale based on the zoom level though, so may be too large when zoomed in.

The precision of transform numbers is limited to a few decimal places for display, but internally the precision is much higher.

Thanks for the fast response, Nate!

I wasn't aware of the shift modifier behavior for fields and it does seem like it will help with a lot of cases, so thanks for letting me know about it. I figured precision behind the scenes must indeed be higher than a few decimal places. It could be interesting to add a checkbox to Settings called "High precision numerical display" for those who prefer to see/be able to copy the unrounded values.

I've attached a scene with assets of exaggerated scale difference. If you zoom in until the 'small' version fills your screen, then select the giant version and attempt to freeform scale it so that the two circles align and disappear, you will see the sort of overshooting behavior I often find myself experiencing specifically when it comes to scaling things. Obviously the solution here is to scale it somewhere close to where I want it, release the mouse, then click again to scale within a more reasonable tolerance. That in mind, I guess this exercise has revealed to me that I tend to try to align things with only one click, haha. Technically, a modifier key could be made such that when pressed it would simulate having released and re-clicked, and recalculate the upper/lower bounds of the scaling sensitivity, BUT that seems quite frivolous indeed when I can just get with the program and start releasing my focused death grip on the mouse more often and start using the field modifier for other cases. :$

Edit: Whoops, didn't notice the attachment failed for being over 2mb (my fault for going a bit too big with the example, hah), so here's a google drive link instead: https://drive.google.com/open?id=1ceNjZJWbF_CxHTCaXGHbfGyNuD5mlNXj