Strangely enough, the Ctrl+Q shortcut I set up for the Selection Tool fails after a period of time?

[dublove]

At first , I thought it was a conflict with other software, but I closed all other software several times and it still didn't fix it.

At first,  it was fine, but after some time of use it failed.

When you restart the software again he is fine again.

It seems to happen a lot since version 19.4, but "V" and "ESC" work.

Anyone interested in helping to try it out?

[Abhishek Rao]

Hi @dublove,

I'm sorry to hear about the issue you're experiencing with the Ctrl+Q shortcut in InDesign. 

To help you better, could you please provide a bit more information? Specifically:

1. What version of InDesign are you using? Please share details about the Operating System as well.
2. Are you using any third-party plugins or software that might be interfering with InDesign? If yes, please try to remove those and then test the issue. 
3. Are there any other shortcuts or functionalities that aren't working as expected? For reference: Learn the default keyboard shortcuts in InDesign (https://adobe.ly/3SIYHH7)
4. Is the issue specific to a single file or happening on a new InDesign file as well? 

In the meantime, I recommend resetting your InDesign preferences as a potential fix. You can do this by holding down Ctrl+Shift+Alt (Windows) or Cmd+Shift+Option (Mac) while launching InDesign. Reference article: Set preferences in Adobe InDesign

If that doesn’t resolve the issue, updating to the latest version and test the issue. 

Let me know if this helps or if you need further assistance!

Thank you,
Abhishek Rao

[dublove]

I have tried all of these methods with no success.
I think it may be that the structure of the new version of InDesign has changed.
I have uninstalled the historical version and cleared everything and reinstalled the latest version.

[leo.r]

All I know is that I can't reproduce this issue on the Mac. I have Ctrl-Z assigned to the Selection tool for many years, and it always works (as do all other custom shortcuts for that matter, save for known issues with script menu shortcuts).

I wonder if you have this problem with the Ctrl-Q shortcut only - or any shortcut you assign to the tool?

[dublove]

@James Gifford—NitroPress 

@leo.r 

@James Gifford—NitroPress 

I found that my ID outright won't let me set the Ctrl+Q shortcut.
Pressing it doesn't do anything either.
I don't see any other software moving either.

It's just so frustrating.
It sucks.

Try yours and see if it's ok?

[leo.r]

I found that my ID outright won't let me set the Ctrl+Q shortcut.

By dublove

The same question remains:

I wonder if you have this problem with the Ctrl-Q shortcut only - or any shortcut you assign to the tool?

[dublove]

I have not assigned Ctrl+Q to any software.
Only ID has used it.
After restarting the computer, just opening ID is fine, after a while it doesn't work.

[leo.r]

I have not assigned Ctrl+Q to any software.
Only ID has used it.
After restarting the computer, just opening ID is fine, after a while it doesn't work.

By dublove

And yet the same question remains:

I wonder if you have this problem with the Ctrl-Q shortcut only - or do you have this problem with any shortcut you assign to the tool?

[James Gifford—NitroPress]

There are some quirks in reassigning keyboard shortcuts. Creating one assignment, under 'default,' does not always work consistently. You may need to duplicate the assignment under other categories for it to work as expected no matter what mode the UI is in.

My example is that I dislike the default PageUp and PageDown behavior, which jumps the display by about a screen height, usually leaving you at some awkward half-view of the pages. (Honestly, I can't figure out what use this is, to anyone.) So I always remap PgUp/PgDn to Previous Spread/Next Spread, so that the jump is always to a full, centered view of the next pages.

However — and this may be a change in later versions, as I don't recall having to do it before v18 or v19 — it does not always work with the mappings in 'default'; I discovered I had to repeat the mapping in "Text." It appears that "default" behaviors are superseded if you have a cursor in text, setting the overall UI model to "Text."

I'd suggest you're seeing a variation of this changing, modal behavior and adding your key mapping to other relevant modes might fix the problem.