Skip to main content
May 5, 2011
Open for Voting

P: Allow for keyboard shortcut customization

  • May 5, 2011
  • 272 replies
  • 15444 views

Customizable keyboard shortcuts in Lightroom would be great. I just find it so confusing that crop and brush tools and things like that have such odd keyboard shortcuts in Lightroom. I understand that changing that all now would be awful for many existing users, but being able to override them like I can in Photoshop would be helpful. Doesn't anyone else out there find they use to wrong keyboard shortcuts in the wrong program?

272 replies

Mendelsphotography
Participating Frequently
January 29, 2024

I agree adobe should make as people said in Photoshop but also like primere it's amazing how you can chose and edit your shortcuts. Can't can't how many times I by mistake pressed or held down CTRL P Or worse X. But no way to switch my flaging keys to something else or even shutting off all together. If you do something to much you can't even CTRL Z it and if you don't have a backup before of your catalog it's all lost. It's about time adobe fixes this. Make and allow us to choose what shortcuts do what and even shut off ones we choose. 

Student photographer, Videographer, and developer.
Inspiring
December 13, 2023

Sorry, back to flogging the dead horse..............  I'm on Windows, so I need to edit the translation file.

I'm looking at the translation file that's in resources/en.

I'm using the translation file in resources/es as a source to try to find the current key 'cause the english file doesn't have anything.

 

I'd like to do 2 things.

I'd like to STOP having the "z" key do "ToggleZoomView"  and have it do EITHER "NextPhoto" (preferrable) OR SetPick/Flagged.  When I press the z I want to go to the next image, just like it does when I press "x" to reject an image.  I don't care if the image is flagged or not, I just want hitting z to go to the next image.

 

If I CAN'T have ctrl+0 do a "fit" on the image, can I at LEAST have it do a ToggleZoomView?  SOMETHING other than toggling the #$%^&* histogram on and off.

 

This is what's in the Spanish translation file

"$$$/AgLibrary/Menu/View/ToggleZoomView/Key=z"

"$$$/AgLibrary/Menu/Photo/SetPick/Flagged/Key=p"

 

Can somebody explain why I CAN'T do

"$$$/AgLibrary/Menu/View/ToggleZoomView/Key=Crtl+0"
"$$$/AgLibrary/Menu/Photo/SetPick/Flagged/Key=z"

 

Are all these things locked somehow, or what IS going on?

 

 

JimButNotHim
Participating Frequently
December 13, 2023

So long as I'm in the keyword input field, letters are just letters and not shortcuts. Windows 10.

johnrellis
Brainiac
December 12, 2023

@JimButNotHim: "I'm sick of thinking I'm in the field to allocate a keyword, typing a keyword that includes D and finding I'm in the develop model. Other built-in shortcuts are equally annoying."

 

Do you find that if you explicitly click in the Keywording box and type "d", you're taken to Develop, or type "f" and taken to Full Screen Preview? A few others (all on Mac, not Windows like you) have reported similar symptoms:

https://community.adobe.com/t5/lightroom-classic-discussions/entering-text-in-metadata-launches-keyboard-shortcut/m-p/14115108

 

The symptoms they describe are clearly a bug. If your symptoms are similar, as a next troubleshooting step, resetting LR's preferences:
https://www.lightroomqueen.com/articles-page/how-do-i-reset-lightrooms-preferences/


LR sometimes soils its preferences file, and resetting it can fix all sorts of wonky behavior. That article explains how to restore the old preferences if resetting doesn't help.

 

Follow up with your results (positive or negative) on that other thread.

New Participant
December 12, 2023

Thanks.

I have installed the plugin, and gone through every category (and subcategory because it only shows the first 100 matching shortcuts). What a lot of work that must have been to create! 

I still cannot get rid of the fact that whilst in the library pressing F goes full screen, L changes to the next light mode, T hides or shows the task bar, Z goes to Loupe view (which is by default the shortcut E), and if in Loupe, G goes to Grid view.

None of those are shown in any of the sections within the edit screens, because I've changed them to blanks.

Single key shortcuts are an abomination. Thanks Adobe.

C.Cella
Inspiring
December 12, 2023

@DavePinMinn 

LrC doesn't allow to "Toggle to Fit"

The behavior doesn't exist.

 

Even via the API the best we can do is "Toggle to 100%" or do "Toggle Zoom" or do zoom step increments/decrements.

 

 

If there is a way to specifically set a precise Zoom to which to toggle to via the SDK then I missed it.

 

 

Inspiring
December 12, 2023

Then I'm not understanding what's needed 'cause this request has been out there for a VERY long time, and I've never been able to do it.  So, exactly HOW do I assign ctrl/0 to have the image "fit", regardless of the current magnification, in Lightroom?  In Windows 11.  Think in terms of "Lightroom for Dummies"...

C.Cella
Inspiring
December 12, 2023

@DavePinMinn 

 

With Any Shortcut you can assign Toggle Zoom to Ctrl + 0

 

 

Or very simply use the existing and more easily reachable kbsc "Z" to always toggle from the current zoom to Fit (assuming you've chosen "Fit" an not "Fill")

 

.

 

 

 

Inspiring
December 12, 2023

Interesting, but doesn't cover the a big Lightroom PITA - ctrl/0 toggles the histogram in both the library and develop module.  I can't recall the number of times I've wanted to "fit" the current image in the available space and hit ctrl/0 as in Photoshop and other tools.  Why Lightroom decided not to follow the already existing Adobe custom I have no idea, but so far I've been unable to find anything that would enable me to correct this #$%^&* decision.

C.Cella
Inspiring
December 12, 2023

@JimButNotHim

 

You can assign any KBSC or remove them but not those in gray.

Those ones are embedded in the code and unmodifiable not even by MacOs.

 

E.g I removed the "New Brush Mask (Brush) KSB completely.

 

 

Edit

 

Actually there are some KBSC that inexplicably can't be assigned but @johnrellis is tracking them, consult the plug-in info section "Known limitations and Issues"