Using keyboard to zoom

[RichZep]

Using a full Windows keyboard, Zoom was Ctr + + or - keys at the end of the keyboard. This option is not available in 2.2.0.1903 for all three programmes. Ctr + = or - work but are nowhere as convenient as using the keys on the number pad on the right.

Hope this makes sense. 

 

[Return]

Tried this out with publisher beta2.2.0.1903 and found that if the numlock is set to off it doesn't work.

[debraspicher]

They changed +/- assignments so that Numpad +/- keys can be set independently. It's in the latest bugfix list:

I personally never used Numpad unless I'm entering numbers, writing code or doing math. I've always treated them as different keypads. Maybe just an old habit.

[Chris B]

It works for me regardless of Num Lock is enabled/disabled. 

However, I used to use both the Num + and - along with = and - but now it seems to be one or the other 😭

[Return]

14 minutes ago, Chris B said:

It works for me regardless of Num Lock is enabled/disabled. 

See my video, as you can see when switching off numlock, the assigned keys don't match and the zooming doesn't work.
I didn't  change shortcuts in affinity or keymapping(software) or the sorts.
This a basic keyboard that came with a previous pc.
 

 

[Chris B]

Thanks Return, I will investigate.

[Return]

I think this endeavor to free up more shortkeys went a bit overboard to make this distinction between numpad keys and normal number keys.
On the other hand most basic windows keyboards come with F(unction)keys which would be better utilized in this respect to have Shift or Alt or Ctrl (or combo)and an Fkey as shortkey.

[Serif Info Bot]

The issue "Add ability to map zoom to = and - as well as + and - on the numpad" (REF: APL-1563) has been fixed by the developers in internal build "2.2.0.1951".
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.