Issue with custom shortcuts

[Sam LaGargouille]

Hello,

I've got a issue with custom shortcuts :

I wanted use the custom shortcuts i use  in the release version to increase or decrease size of brush. (French keyboard - numeric key "-" to decrease and "+" to increase)

the shortcut to increase works find, but not the decrease shortcut.

I've got no issue in other versions of affinity with this shortcut and in 2.1 beta shortcuts created with "-"  have bugs or don't work

[Chris B]

Is this with an AZERTY layout? If so, I've reproduced this.

I mapped Decrease to - and Increase to + (which actually showed as = in the app Shortcuts) and Decrease does not work:

I then tested this in the Retail version and it works as expected. I'll log this with the developers.

[Sam LaGargouille]

Thank 's for trying on your side to validate the problem, and  for the feedback to the developers.🙂

[Sam LaGargouille]

Hello again, same issue in the release version, but i've find a hack, so if any people have similar issue perhaps, it will help :

I switched to QWERTY and I assigned the shortcuts using the position of the - and + keys on this keyboard config. Then I switched back to azerty, and miraculously, the attribution works again when i use  - and + on num pad.

[Chris B]

Thanks. I've updated the bug report with this new info.

[Andy05]

I can confirm, this is also an issue with a German keyboard layout (QWERTZ). The workaround with temporarily switching to a QWERTY layout for setting up the shortcut doesn't work for me. I now assigned some combination, which work similarly on QWERTY/Z layouts (e. g. CTRL+SHIFT+ALT+K), so I can use that as a hotkey on my graphic tablet.

[Affinity Info Bot]

The issue "Decrease shortcut fails in AZERTY layout" (REF: AFP-6102) has been fixed by the developers in internal build "2.2.0.1900".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.