Skip to main content
zbarnes_aw
zbarnes_aw
Participating Frequently
December 2, 2019

P: Actions no longer run via keyboard shortcut unless an active document is open

  • December 2, 2019
  • 12 replies
  • 558 views

Our company relies upon a number of batch operation scripts (.jsx). The most recent update (PS 21.0.1) breaks a very convenient feature.

What we want fixed
- Run an action via keyboard shortcut from the home screen of Photoshop (no documents open). [1 user operation]

What we're dealing with
- The action needs to be run via the menu (File > Scripts > Browse > Find Script)  [4+ user operations]
- Open a document, then use the keyboard shortcut (this doesn't work for batch operations unless the script is altered to close the active document before running)

    This topic has been closed for replies.

    12 replies

    J
    jaypot21
    Participating Frequently
    September 20, 2020

    I encountered the same problem. I'm having a new imac. After installing the photoshop to it, the shortcut keys for the actions is not working. I searched but none came to fix the issue. Then I suspect that the imac's internal function keys is affecting it so what I did is I went to system preference of imac> tap keyboard> keyboard tab> check Use F1, F2, etc keys as standard function keys

     

    see attached image

    J
    J453
    Legend
    February 19, 2020
    This should be fixed in the 21.1 update that went out last night.
    J
    J453
    Legend
    December 4, 2019
    Perfect. I know what's going on now. Will look into it.
    zbarnes_aw
    zbarnes_awAuthor
    Participating Frequently
    December 3, 2019
    Whereas 'command' works without adjusting the home-screen option.

    zbarnes_aw
    zbarnes_awAuthor
    Participating Frequently
    December 3, 2019
    Runs properly using shift from 0:27 onward

    J
    J453
    Legend
    December 3, 2019
    Yeah. A screen recording might help. Thanks.
    zbarnes_aw
    zbarnes_awAuthor
    Participating Frequently
    December 2, 2019
    If you need more detailed information (such as a screen recording), I can still reproduce the error on my end when I disable your workaround
    zbarnes_aw
    zbarnes_awAuthor
    Participating Frequently
    December 2, 2019
    10.14.6 Mojave
    As stated above, I'm expecting this is a cache (or some other local file) related error that's probably tough to reproduce. It smells that way to me since adjusting the assignment from the Shift to Command button was a successful workaround. But when it was changed back to Shift, the error occurred again.
    J
    J453
    Legend
    December 2, 2019
    Can you confirm what OS/version you're running on? On macOS, all the combinations I used worked. 
    zbarnes_aw
    zbarnes_awAuthor
    Participating Frequently
    December 2, 2019
    Thanks for the quick response. Good thought. That does it
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices