Inconsistent hotkeys / usage between Adobe products

  • 1
  • Problem
  • Updated 2 months ago
I've been told to mention my issues here, and so I am. I've found it pretty infuriating and frustrating switching between various Adobe products to find that simple elements are completely different, not to be found or the hotkeys are changed... I understand some hotkey differences based on more heavily used actions or such but for manipulating a canvas (zooming in/out or horizontal scrolling) this should be the same in all products...

https://twitter.com/timbeaudet/status/1049645209896796160

Apparently this is "by design". I can't think of a single reason one would design Photoshop to use ALT-scrolling for zoom and then consciously choose to design/make Animate use CTRL-scrolling. The only reason would be "legacy" reasons of having purchased some software that behaved differently and not changing it. Please, consider making the Adobe software more consistent across the default setups, it helps a user move from one application to another without getting wildly frustrated.

I had similar issues with the color picker in Illustrator vs that in Photoshop; why are these different by default... 
Photo of Tim Beaudet

Tim Beaudet

  • 2 Posts
  • 0 Reply Likes

Posted 2 months ago

  • 1
Photo of Cristen Gillespie

Cristen Gillespie

  • 1434 Posts
  • 414 Reply Likes
This is actually why we all keep asking for every app to let us customize our keyboard shortcuts. If they did that, they could even ship with the default keyboard shortcuts for the various apps, so if you use PS, but not so much After Effects, you could choose PS defaults and override AE for identical functions.

There are requests (Ideas) here for customizing. The problem with Adobe doing it all is they'd be making each and every customer flaming mad. I use Photoshop most. Photoshop uses Cmd-D to deselect. Everyone else uses Cmd-Shift-A. I changed PS's shortcut for that one, while other people want to change other apps to match PS because D for Deselect makes more sense to them that modifying Select All.

I do agree with you that newer programs like Lightroom adopting entirely different shortcuts from their cousin makes no sense to me. IIRC, when it first came out, LR didn't even talk directly to Photoshop. And don't get me started on the decision someone made to add shortcuts to Camera Raw that didn't match Photoshop, but as they added features in Camera Raw, that's how it developed. Drives me nuts.

By now however, a lot of people have learned whatever shortcuts they use most often in any given application, and the only way to make it workable, imo, is to allow us to customize. I know I, for one, truly do not want Adobe telling me what a shortcut should be. Half the time they try to do that in an application that has custom kbsc, I want my own, not theirs, anyway. And you can bet if they DID come out with a general purpose set of kbsc, they'd be constantly changing it to meet whatever the prevailing winds are at the time, the way they do with the interface skins, driving us even more bonkers. LOL
Photo of Warren Heaton

Warren Heaton

  • 168 Posts
  • 73 Reply Likes
InDesign made a small step toward this with CC2018.  The application prompts you to leave the shortcuts as is, use Photoshop shortcuts or use Illustrator shortcuts.
Photo of Tim Beaudet

Tim Beaudet

  • 2 Posts
  • 0 Reply Likes
As I said I get legacy issues and current users getting weird about it, but keep a legacy hotkey setting for those users. I'm coming into the Adobe family as a new user, and honestly it feels quite odd to me that a family of products have separate hotkeys per application. There are ways to customize this, but consider NEW users.
Photo of Cristen Gillespie

Cristen Gillespie

  • 1434 Posts
  • 414 Reply Likes
> honestly it feels quite odd to me that a family of products have separate hotkeys per application. >

As a new user, I'm sure you see this family of products as a family. Their marketing speak does somewhat pretend to that. The reality, as you've noted, is that they're a family in the same sense that your extended family, including relatives by marriage, are a family, but not all living in the same house. The history is that they were separate applications, not even related they came from different companies, developed separately, barely working together at all, on different release schedules that constantly broke the slender ties that bound them, before they tied them together with the Creative Suite. So much more important than imposing a set of kbsc on all the apps was  needed, such as getting files from one app into another. That wasn't working well at all, and now you barely,  or rarely, have to do anything to your file to make it possible for another of the apps to make use of it. In itself a pretty massive undertaking as each app develops features the other apps know nothing about, but have to be able to ingest.

Let me show another reason why convening a convention to establish a set of governing kbsc wouldn't work long term, or even carry over to the next few releases—besides how angry it would make an established user base.  Let's imagine that this set of kbsc was in effect a few years ago. All the functions that were the same throughout the apps had the same kbsc. All the features exclusive to a single app, had whatever kbsc were left over to assign to their specific features.

Then After Effects invents Puppet Warp. They assign one of their "free" kbsc to the function. A couple releases later, Photoshop puts in place their own version of Puppet Warp. And look for a free kbsc to assign to it. The one AE assigned has already been assigned to a long-standing PS feature. Do they take it away from that feature PS users use daily in order to assign it to Puppet Warp, a much less commonly used feature? Two releases after that, Illustrator gets on board with their version of Puppet Warp. How does that go, when it comes time to take away a shortcut their users have used for 20 years because After Effects was the first to invent Puppet Warp and to assign the kbsc to it? And the new user then comes along and says, "why doesn't Puppet Warp have the same kbsc across all the apps?"

What you're asking for will break down time and time and time again as the apps develop, then share, features. What I wish for is they would share more of the interface and behavior of these features than they currently do. Type belongs to ID. Video to AE or PP. Vector to AI. Raster to PS. Make them behave more like the main app that develops them. (In fact, though, it was a long time before PS's Pen tool worked more like AI's—talk about confusing the customer.)

But kbsc? It still sounds to me that the only long-term solution is the one they already developed—perhaps working to share kbsc sets  between apps more, but otherwise, if they mess with the way it works today, I'd say it should be towards allowing more more custom shortcuts and relaxing their rigid rules about what keys can be assigned to create them.