There should be a copy paste from a right click.
I posted a simple example of adding those commands to the context menu
(over in the Ruby API category):
⌠and I like the way that SketchUp Free puts an edit toolbar at the top of the context menu.
The desktop SketchUp edition could benefit from something like this as well.
Iâm not a fan of that approach at all. Itâs great in theory but it doesnât display the shortcuts the way menus in Windows usually do, meaning computer newbies donât learn them as easily.
<off-topic>I really donât know why SU doesnât show the universal Ctrl+Z for Undo and Ctrl+X for cut</off-topic>
1 Like
We who do not use shortcuts as much, are obviously in the context menu in the first place, to choose a command from the menu, not learn a keyboard shortcut.
Why should I (a 10 yr user) or other experienced users, suffer without a workflow enhancing feature, because some newbie(s) are too lazy to read the dang manual or print out the quick reference card and post it next to the monitor.
Positions like this are a policy of âpander to the newbie and deny ergonomy to the experienced user.â
Where is the universal law that says context menus are a tutoring device anyway ? They are not.
(Iâd even like an application option to switch off the shortcut display in the context menu, as itâs just visual clutter for me, that my brain has to ignore.)
âScuse my passion here, but, Iâm tired of hearing this TWADDLE that productivity enhancing features cannot be implemented because all UX must pander to the poor lilâ newbies.
What I said was not a theory ! It is a fact that it will be quicker to get to the main edit commands (less movement of the hand and arm = less carpal tunnel / less tendinitis of which I have suffered in the past from doing excessive CAD work.)
If it wasnât a valid UX feature it would not have been implemented in the web edition. It condenses the context menu, and puts those common edit commands right at the top, where they can be used with a minimum of movement.
With regard to menus, SketchUp could also do what MS Office applications have done for years and have two levels of menus and such. Users can start out in ânoviceâ mode, and switch later to âexpertâ mode (or whatever a good name is.) It already has novice toolbars, why not menus to go along with it ?
But do not force the rest of the professional world to forever run in novice mode !!!
A good UI doesnât need a manual because it is self explanatory. Manuals explaining a UI are of the past. There can be manuals and tutorials describing different workflows and how to organize a project but how to interact with the program should be obvious from it.
I think every user use a menu primarily to click whatâs in it, not to find a shortcut, but being reminded of the shortcut each time you open the menu is a great way to pick it up, with no effort needed. These cues should be visible in the UI itself so people can improve their workflow without having to read a manual.
Iâm not pandering newbies at the cost of experienced users. Iâm against having these commands in the menu in the first place as it a) discourages new users from learning shortcuts and b) clutters the interface for all uses (advanced or not).
Using a shortcut is much more ergonomic than pressing anything with the mouse, even if itâs really close to the current position of the cursor. Moving the mouse with precision onto a small clickable area, no matter how short the distance, puts more strain on the body than moving the fingers to a keyboard key. I suspect the web UI was designed with the intention to be used without a keyboard.
I my view having a big switch to toggle between novice mode and advanced mode is really quite stupid. It becomes a giant threshold to overcome; semi-advanced users would put off changing it and those that try it may even switch back because it adds to much new noise at one single time and hinders productivity in the beginning. I think gradually adding complexity, by installing new features as plugins and add toolbars independently, is a superior approach.
1 Like