Preselecting a curve then calling Offset. Normally one can then type in a new value for the offset if it is different than the previous stored value, hitting Enter updates the offset distance at the command line and the on-screen preview. However in the latest Beta, all I get is a ding sound when I try that and no update. And, I cannot cancel the command at that point with Esc… if I right click somewhere in a viewport like to pan it, then I can cancel with Esc. Something is getting the focus wrong at some point.
Post-selecting the curve does work correctly, as does mouse clicking the command line distance option directly to change it.
I’m seeing the same behaviour in R9 as in R8, but that’s just starting Rhino, creating a line and running offset on it per your instructions. So, any thoughts about the context you are doing it in that might cause yours to differ?
Preselecting a curve, starting Offset, entering a different offset distance, and completing the comman is working normally for me in BETA (9.0.26202.12303, 2026-07-21). I don’t have any command aliases or macros, and the only plug-in which “does not ship with Rhino” is ClippingBox.
Hmm, I have two sessions open and it is not working correctly in only one of them…
I will now try to close the Beta and re-open that file and see if it is just some kind of one-shot gremlin, file related or what…
OK, closing Rhino and reopening the same file and now it’s working correctly. One-shot gremlin. Thanks for the responses, will keep an eye out for any similar occurrences.
I just ran into this again with a different command - just a simple Box. Ran the command from a button and then typed 0 to set the corner at the origin and all I got was a ding. And I couldn’t cancel with Esc. Exactly the same symptoms. Panning a viewport with the RMB resets it (other actions might also, haven’t tried), so IMO it is definitely some glitch that is temporarily stealing the focus and not allowing any kind of command input. @gijs
I have figured how to reproduce this consistently - at least on my setup (Windows Beta).
Default workspace
Make a new blank file with 4 viewports showing.
Make the Top viewport active (click on the viewport title)
Move the mouse to the LH side toolbars and choose the Circle tool by clicking on the toolbar icon.
Now, move the mouse cursor over the Perspective viewport - without clicking anything - so it becomes active (the viewport title bar highlights)
Now type “0” and Enter to set the circle center at the origin.
If your setup works like mine, and you follow the above steps exactly, you will get a “Ding” when you hit Enter and nothing will happen. You can click the mouse to set the center, that works, but typing a value at the command line doesn’t. I can repeat this every time by following the above steps. It does look like a focus-stealing issue.
If you go to any of the viewports other than the one active prior to selecting the circle tool you consistently get the same problem. The one active prior to selecting the tool need not be Top.
If, after failing to get the text into the command line, you move the cursor to another viewport, text entry will work normally. This includes moving the cursor out of the failing viewport and back in again.
It doesn’t have to be the circle, any tool that creates an object and requires a first coordinate does the same.
Hope that gives a lucky developer more to work on.
Jeremy
