[Win] Q key not selecting healing brush
Running 16.3.2 I noticed today that my Q key no longer selects the healing tool - wanted to check with others on the forum before posting a possibly silly bug report.
The heal tool gets automatically selected when selecting a healing layer, but if you switch to the eraser to modify an operation, to switch back you need to press Q by default. I checked if it was bound to something else (It is not), other than the Speed Edit control, which is default.
Anyone else observed this, or something like it ? I read through the application.log and there wasn't anything incriminating in there, so I'm a bit lost as to how to pick it apart and get it working!
-
You could go to Edit Keyboard shortcuts in the Edit menu and check whether Q is set to do that. If it isn't, you can set it.
Ian
0 -
Yes I checked there, I also rebound it to another key (N) which works fine, however when the key is rebound to Q (and I checked for conflicts, too) it does not work.
I suspect Q is conflicting perhaps with the SpeedEdit keys, however the logs don't throw up anything revealing. Does Q for healing brush work on your system?
0 -
Speed Edits require long press (press-n-hold) vs Q key for switching to heal tool. Are you using the default keyboard map or a custom keyboard map?
Try switching to the default keyboard map and see if keys work as expected. If so, perhaps the custom keyboard map is corrupt.
1 -
Ooh, good shout on the defaults, I tried remapping but didn't think to switch back to the default keyset to check!
The default set works fine, so now the question is - how did my custom set become "Corrupt" and how to I remedy it - I'm really not endeared to the suggestion that I go through the summary printout line by line recreating my keybinds...?
According to the UI there are no other keys bound to Q, but obviously *something* is tripping it over.1 -
I picked through the keylist printout, and I have a bind no longer shown by the keybind UI for "Corresponding Points" lurking in there, perhaps a legacy echo from C1 v7/8 - I suspect that's the culprit!
Thanks for the reminder to check the defaults, I guess I'll have to work through the printout and rebind a new set in the morning.1 -
Look for your custom key map in the app prefs folder. If it's a text file you might be able to remedy this by editing the text file vs rebuilding a custom map. Make a backup copy!
0
Please sign in to leave a comment.
Comments
6 comments