Osnap and SelectionFilter have always taken a lot of screen space, and checkboxes typically don’t work very well in horizontal mode. We’re experimenting changing these to state buttons similar to the buttons in the status bar.
Let us know if this works for you. It will take some time to get used to it, keep that in mind.
_TestOsnapToggles
We are trying to differentiate OSnap and Selection Filters visually. Many users are getting the panels visually mixed up since they appear very similar and are docked together by default. The yellow “selection” color seems to help with that.
Color is always user subjective for a multitude of reasons but @Akash what color for dark mode would you suggest? We don’t have anything set in stone yet, we’re just playing with the concept.
Regarding colors, to eventually have it user defined is best, but as far as default… one options is to also use the OS color [like the view buttons , or a different [then Osnaps] gray
[to keep is visually gentle ]
No… i don’t even remember where to change that… But i can imagine there’s a challenge in finding an auto invert color that will work for both modes. That also why i think changing the fonts color is better then changing the background [you already have a light and a dark gray shades incorporated as background. Why add a 3rd colour to the background …? it’s a bit confusing .
PS: the double filters panel bug visible in the screen recording, is an old bug, reported many times… wouldn’t it be great if it was fixed while the filters and Osanp panels get this much deserved attention now.
Yeah we’ll get the double panel spawning cleaned up.
Thanks for the feedback. As we mentioned this is an experiment to try to visually separate the buttons in this panel from OSnaps and associate them with “Selection” which typically uses a yellow color around Rhino. We are experimenting here because we receive many support questions where users have confused this panel with OSnap. Nothings set in stone yet. It’s why this is a hidden command for everyone to play with. If the color option is our worst problem we’re probably on the right track. And if we can get them compressed enough to fit them along the bottom it’s an even bigger plus imo.
Regarding compressing farther : we have a disable button and right under it in the status bar we have a Filter button … Is it really needed to even hav that Disable button ? merging It’s functionality into the Filter button will save space [and some confusion]
In addition figuring an abbreviation for the Sub-object button will also free some space.
Localization is the real issue with whether or not they’ll work out on the bottom. We’ll have to be able to fit them in all languages in order to be the default location.
I’ve been running them double stacked vertically on the bottom with longer strings to see how annoying that might be. I like it over the dedicated left hand panel, but its probably too much for 1080p monitors.
I’m sure this won’t change…
But.
Everybody can easily learn 10 words in english… Why not keep UI buttons in English? helping to simplified and unify the Rhino UI