Just comparing the screenshots in the post, I think I prefer the submenu personally. When you have as many actions defined as the author does, it gets a bit unwieldy. I have one simple Automator...
Just comparing the screenshots in the post, I think I prefer the submenu personally. When you have as many actions defined as the author does, it gets a bit unwieldy.
I have one simple Automator action in my submenu that I set up years ago and still use from time to time. Mentioning it here since it wasn’t in the list of suggestions in the post… it just pops up a dialog with a few checksums for the file. MD5, SHA-1, and SHA-256 if memory serves. It’s not something I need often but it’s a lot more convenient than assembling a shell command every time.
Not at all. It's far quicker and easier to do a vertical movement down a single menu, than a zig zag down-pause-across-pause-down to a sub menu, which is so much more difficult in terms of both...
Not at all. It's far quicker and easier to do a vertical movement down a single menu, than a zig zag down-pause-across-pause-down to a sub menu, which is so much more difficult in terms of both cognitive load and motor control. When you're doing it multiple times a day for various different things the submenu gets old fast. But if you've only got one that you use infrequently you're not going to have much, if any, submenu friction.
A single order also makes it easier to remember position so much so that I choose the correct menu for a specific file by muscle memory and don't really have to read the screen.
Also, the items in the context menu are all relevant to the current selection. So by design there will be different items for a different file type. They're not unwieldy but rather all right where I need them to be.
ps: I also have an item to show hashes, which I do by opening my own hash app (that bundles off the shelf tools) all shared I'm the repo.
That Context Menu app looks awesome. I am very excited to whip up a few Automator scripts that I don’t have to dig into submenus to use.
Just comparing the screenshots in the post, I think I prefer the submenu personally. When you have as many actions defined as the author does, it gets a bit unwieldy.
I have one simple Automator action in my submenu that I set up years ago and still use from time to time. Mentioning it here since it wasn’t in the list of suggestions in the post… it just pops up a dialog with a few checksums for the file. MD5, SHA-1, and SHA-256 if memory serves. It’s not something I need often but it’s a lot more convenient than assembling a shell command every time.
Not at all. It's far quicker and easier to do a vertical movement down a single menu, than a zig zag down-pause-across-pause-down to a sub menu, which is so much more difficult in terms of both cognitive load and motor control. When you're doing it multiple times a day for various different things the submenu gets old fast. But if you've only got one that you use infrequently you're not going to have much, if any, submenu friction.
A single order also makes it easier to remember position so much so that I choose the correct menu for a specific file by muscle memory and don't really have to read the screen.
Also, the items in the context menu are all relevant to the current selection. So by design there will be different items for a different file type. They're not unwieldy but rather all right where I need them to be.
ps: I also have an item to show hashes, which I do by opening my own hash app (that bundles off the shelf tools) all shared I'm the repo.