There’s a worrying trend where the context menu is becoming less and less contextual.
This was okay until I recently started misclicking “Insert Part” due to the added “Use Local Space” item.
The context menu currently stands at an amazonian ~450 pixels tall and spans almost half my screen.
Clearly the situation has gotten out of hand and something must be done!
I’d suggest hiding the actions ‘Use Local Space’, ‘Swap Connections’, ‘Swap Attachments’, ‘Union’, ‘Negate’, Separate’ and ‘Zoom to’ unless they’re applicable to the selected instance(s).
This is actually probably intentional. A lot of UX people consider what you suggested bad practice because it moves buttons around. When I click on a part I might select the 9th option down, but when I click on a local script the 9th option may have been moved to #5 or something and now I have to fumble around looking for it instead of habitually clicking slot #9
2 Likes
Many programs that’re considered well-designed do actually change context menus based on context.
I’d also like to suggest sections being hidden when all of the actions within them are greyed out.
I feel the Union/Negate/Separate actions need their own section, anyway. That’d play nicely with that.
In that case, common options should come before contextual ones. By common I mean options that all objects share.