“fixed” … but also with a status “closed”! 
Is the development about this already finished? I hope not. What about SubDs?
I wanted to discuss about it but never got a reply from Joshua..
The new “widget” is interesting (now even as 2D elements on screen space, nice!) , but the arrows have an absolute size related to the control net wires size.
This is not good, as sometime you micro-manage control points really near the geometry, and such arrows spawn too big and completely out of the screen.
The usual fixed scree-size as the normal gumball would be good.
Also, I updated my Rhino 9/WIP and TestMoveUVNWidgets command no longer works.
With this thread I wanted to suggest on developing a proper c / c++ / c# class for a new type of gumball, to be accessible also for users through SDK or rhinocommon.
I see Joshua did something in that direction… (or not?)
For surfaces TestMoveUVNWidgets was good (even though it’s an additional layer of abstraction over an obsolete command like MoveUVN… imo).
But for SubD it still generated a fixed set of 3 arrows, strictly orthogonal each-other …
Please: literally recreate a better “widget” from scratch and replace it everywhere (see my third post about fillets UI/UX too) and make it accessible for users.
Current gumball class is not enough for 2025.
Please, SubD need better workflow for micro-adjusting control points. Few clicks. Fast. Simple. See other softwares.
Aim for the stars!