And an Old one, reported long time ago
I cannot click a layer continuously On and OFF without having to move the mouse some pixels between each click. This is super annoying when I just quickly want to check whats on the layer.
Same goes for lock icon. And perhaps other items as well, I havent checked.
And another old one, reported long time ago:
Highlighting layer with nested layers does not work (Click + Enter)
Only Layers with no nested layers highlight correctly.
Hello Hans, thanks for reporting, pls run _SystemInfo in Rhino and post back the results.
I made a dimension and started changing the height, which works as expected,
From the image you are posting, it is not clear to me what is happening at your end. Does your dimension stay put and the changed appears in red? Is red your selection color?
that behavior I cannot repeat here.
I could not reliably repeat this, but I do see some odd things happening, and I haven’t found a pattern yet what triggers it. Here it sometimes even locks up every edit I want to make. But a restart of Rhino fixes it. Is the behavior you are seeing consistent in that file, even after a restart of Rhino? If so having that file would be extremely helpful.
I must say that I never edit layers names with the Enter key. I wonder if you are seeing that behavior as well if you only use the mouse to rename the layer (as a test)
The new height appear in red. Both old and new height show simultaneously
Yes red is my usual selected color.
Try typing in the new height instead of using increment arrows
This behavior is consistent in all my files. Restart doesnt change anything.
This is an old bug for me, more than a year.
Both on Mac Intel, M1, and now M4
I just tested with right-click / contextual menu “rename layer” - same behavior !
I have a 6 button mouse, with a button assigned to Enter. Really fast and useful
What do you mean rename layer using mouse ? Double clicking doesnt do anything here
@ohlers regarding the layer editing, Do you get that too when your mac is connected to a single monitor only? This is a mac mini, correct?
Click, wait, Click
That’s what I did, changes instantly.
Just as a test, it would be interesting to see if any of these problems go away when there is no additional monitor attached so that we can narrow this down. Other things that need to be tried is to detach as many as possible devices and see if the problem persist, again to rule out as many options as possible.
I’ve logged the layer issue here, even though I cannot reproduce it exactly as you experience it RH-88035 Layer properties cannot be changed sometimes
@ohlers regarding the mouse click on light bulbs: what I do see is that there is a little delay before I can click it again, but I don’t need to move the mouse.
Yes this is a MacMini M4, but I had the problem with Layers and Icons on a MacBookPro M1, and I seem to remember this was an issue already at V8 launch, where I had a Mac Mini Intel.
The Dimension weirdness is new, since last V8 upgrade.
No change with only one monitor. Peripherals are necessary: Mouse, Spacemouse, Keyboard, ext HD. Same issue:
just tried that - it works but - wayyy too slow !! We are not in the retirement home yet !
I really prefer renaming layers using Enter. (consistent with all Mac Finder behavior)
Yes I have the same - but that is way too slow too - how do i set the delay to a bare minimum ?
the video i made to this post is with this rythm :
click - enter
click - enter
click - enter etc.
as you can see, layers that are nested just turn grey, while single layers highlight.
I know, but you mentioned you were using the Enter programmed on your mouse, correct?
I want to know if the same happens with the Enter key on the keyboard.
ah - yes its the exact same thing
(I use USB Overdrive to assign the Enter command, so its the same Enter that the Keyboard is doing. It is a really cool app, especially with a multibutton mouse https://www.usboverdrive.com/ )
and before you ask: YES its all the same , even with USB overdrive disabled
Layers with child layers cannot be highlighted to change name, using Enter.
Only single layers can be highlighted and name changed using enter.
But that issue does not affect the lightbulp or lock icon. The problem with those icons is another matter, that we discussed:
Lightbulp and Lock icon cannot change state fast enough. The delay before they can accept another click in the same pixel position is too long.
…
And then there is the third issue, that I have reported, that you dont seem to respond to:
Changing dimension property text height result in both old and new height being displayed, and the new one is highlighted. I will then have to click the old one, to get that to disappear, and click the new one, to make it shift from highlighted to normal.
I don’t think I am mixing up bugs here. The 88035 is not exactly the same as what you are experiencing, in my case everything just locks up, I cannot even click the light bulb or lock icon once + I cannot change the layer name. As stated, I haven’t managed to find a pattern to repeat this bug. Again, I could not exactly repeat the bug you are experiencing.
As for the light bulb/lock, this is logged as a performance issue currently, but I found that changing the mouse speed double click setting in OS settings has a great effect on it.
The third issue, I did respond to: I cannot repeat that here, neither could @wim
When we are logging bugs, the chances of getting a bug fixed that is not repeatable is close to 0. It could be model related, or maybe related to the annotation style you are using. If you have a file where you can reliably reproduce it in, even if you think it happens in every file, it is still useful to send that file. It happens very often that we cannot reproduce it until we receive a customers’ file.
do you mean the radio buttons? Those only determine which is the current annotation style. When you draw a new annotation it will default to the one you have chosen there. If you want to change some setting in an annotation style, you will need to click on that annotation style. But now that I write this, I can see that that can be confusing:
In the Rhino UI, any setting that is blue means it has changed values from the default (I assume you know this, but mentioning it here for completeness)
one more thing, since you are having this issue on multiple machines, it might be triggered by something on your end. The only way to debug this is to see if you can still repeat it with a setup that is as bare bone as possible. If you can’t, then start adding your peripheral devices one by one
