I’ve been using Rhino 8 since the morning it was released and so far one of the biggest issues slowing me down is the command line often loses focus when I interact with the layers panel.
So for example: if I right click on a layer and click on Select Sublayer Objects, then press the Delete key:
Nothing happens at all.
If I repeat that process then the layer itself deletes.
If I right click in the viewport to slightly move the camera, then delete actually deletes the currently selected objects, which is the intended behavior, like how Rhino 5, 6, and 7 behave in that scenario.
That’s the simplest example I have, but it is happening pretty often throughout my design sessions. Especially since I use a 3D mouse to move the camera, so I don’t often click in the viewport. This behavior also happens with macros I’ve saved.
Same issue here. If I click anywhere in the layer panel, I can usually go ahead and start to type a command and it will populate the command prompt automatically. Now, I have to stop and make sure I’ve clicked in the command prompt to activate it. Hoping this reverts back to the efficient way before my muscle memory adjusts :). Thanks for addressing this
I see in the latest Service Release 3 that RH-78615 is marked as fixed and I realize now that there was some miscommunication on my part. The command line losing focus problem I’m talking about happens with ANY command. Delete not responding in a repeatable way is a separate, yet related issue I realize now.
What I’m talking about here in this thread is that after clicking something on the layer panel, the focus is now stuck there, and typing now no longer registers in the command line, nor does hitting the F-key command macros respond with launching their commands. Literally nothing can happen until you left click somewhere in the viewport, and now the focus shifting there allows for the command line and command macros to respond correctly. I should have worded this better at the beginning.
This bug is massively slowing me down in RH8 because I interact with the layers panel extremely often. I’ve been using Rhino for going on 7 years now and my muscle memory is colliding straight into this bug.
this issue seams still not be solve.
it feels really unfluent.
please @pascal@Gijs make sure that those really ugly paper-cuts regarding mouse / input focus are solved quickly.
(8.3.24009.15001, 2024-01-09) on windows 10
the following workflow is repeatable here:
rename a layer other then the active / current layer (not sure if this step is nescessary)
set another layer as active / current
start typing a command (“_extrudecrv”…) - nothing happens - the focus / input is nowhere.
An additional click in the viewport or the commandline is needed.
this feels really bumpy / unfluent / ugly (sorry I miss the correct english word “holprig” I would use in german)
hard to catch keyboard-input that has no effect on a video:
after changing the name of 2 layers and setting a 3rd layer active,
I try to type something, that is not visible on the screencapture…
an additional mouse click is needed to get the focus back to the commandline.
I, too, am having an issue with this. It literally just needs to work like the previous versions wherein the command line is always accepting keyboard inputs. Can this be fixed?
Is it only with command typing, or with running shortcuts.
I recently logged this issue that might be related RH-81217 Shortcut doesn’t work when Layer Panel has focus
Yes.
On both platforms, Mac and PC, Version 8.5
Last week I was teaching an introduction / Beginners course. For one participant on a Pc is was a continuous problem.
maybe it got a bit better ?
I also notice, that changing layers while a command is active has sometimes those commandline- problems, so entering a distance or a numeric point input needs an extra click in the viewport or commandline.
I still can not provide a repeatable workflow.
also see here
and this old focus problem which is 100% repeatable
maybe related ?
and the not-disappearing tooltips are also still there and repeatable - and also maybe related ?
@Tom_P if you have any info or are able to record on Mac that would be helpful. I tried hard in different versions but it seems to just always work as expected.
my alchemistical, non-scientific, glas-bowl guessing - it has to do with:
multi documents open
rhino running for a few hours without restart (so maybe the bug is close to the memory leak that happened in early V8)
maybe with a second monitor I use while teaching
there are a few Mac-symptoms that might be linked:
if rhino ran for several hours, sometimes, nightshift (monitor-color adaption - less blue) is not activated (reported here)
with multiple rhino documents open, start a command in one document, do not finish the command, (for example keep arrayPolar in the preview-state) go to another document - this sometimes / quite often results in an unresponsible or limited responsibility - state of the second document…
additional mouse click for SetPt or BlockEdit - see above…
but really this is just guessing… as soon as I find something that is repeatable I will report.