Keymapping, shift vs non-shift

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Keymapping, shift vs non-shift

Stephan Eggermont-3
On my keyboard I have '+' in two positions: once over the '=' in the
alphanumeric part,and once as a separate key on the numeric part.
When I do a

self bindKeyCombination: $+ command mac | $+ ctrl win | $+ ctrl unix
   toAction: [ self increaseFontSize ].

that only works for the numeric '+'.
Is that supposed to be the case? The problem is that it forces me to
know about the keyboard layout to define shortcuts.

Stephan



Reply | Threaded
Open this post in threaded view
|

Re: Keymapping, shift vs non-shift

Nicolai Hess-3-2


2015-12-14 11:16 GMT+01:00 Stephan Eggermont <[hidden email]>:
On my keyboard I have '+' in two positions: once over the '=' in the alphanumeric part,and once as a separate key on the numeric part.
When I do a

self bindKeyCombination: $+ command mac | $+ ctrl win | $+ ctrl unix
  toAction: [ self increaseFontSize ].

that only works for the numeric '+'.
Is that supposed to be the case? The problem is that it forces me to know about the keyboard layout to define shortcuts.

I stumbled across this too, I don't think it is supposed to work that way.
 

Stephan




Reply | Threaded
Open this post in threaded view
|

Re: Keymapping, shift vs non-shift

Guillermo Polito

On 14 dic 2015, at 11:23 a.m., Nicolai Hess <[hidden email]> wrote:



2015-12-14 11:16 GMT+01:00 Stephan Eggermont <[hidden email]>:
On my keyboard I have '+' in two positions: once over the '=' in the alphanumeric part,and once as a separate key on the numeric part.
When I do a

self bindKeyCombination: $+ command mac | $+ ctrl win | $+ ctrl unix
  toAction: [ self increaseFontSize ].

that only works for the numeric '+'.
Is that supposed to be the case? The problem is that it forces me to know about the keyboard layout to define shortcuts.


So you mean that in order to make + in your +/= key you must press shift? And then (ctrl +) does not match (ctrl shift +)?

Then I’d say it is a bug/unimplemented feature...

Hmm, maybe shift only has to work as a modifier for alphanumeric characters...


I stumbled across this too, I don't think it is supposed to work that way.
 

Stephan





Reply | Threaded
Open this post in threaded view
|

Re: Keymapping, shift vs non-shift

Stephan Eggermont-3
On 14-12-15 12:13, Guillermo Polito wrote:
> So you mean that in order to make + in your +/= key you must press
> shift? And then (ctrl +) does not match (ctrl shift +)?

Indeed.

> Then I’d say it is a bug/unimplemented feature...
>
> Hmm, maybe shift only has to work as a modifier for alphanumeric
> characters...

That sounds like a good first step.

It might be even more difficult than that, though. On many non-english
keyboards there are other key combinations with modifiers like AltGr to
get to other characters, and dead keys. German and French have [] and
{}. I don't know what characters are beneath the shifted versions of them.

Stephan


Reply | Threaded
Open this post in threaded view
|

Re: Keymapping, shift vs non-shift

Peter Uhnak
In reply to this post by Guillermo Polito
On 12/14, Guillermo Polito wrote:

>
> > On 14 dic 2015, at 11:23 a.m., Nicolai Hess <[hidden email]> wrote:
> >
> >
> >
> > 2015-12-14 11:16 GMT+01:00 Stephan Eggermont <[hidden email] <mailto:[hidden email]>>:
> > On my keyboard I have '+' in two positions: once over the '=' in the alphanumeric part,and once as a separate key on the numeric part.
> > When I do a
> >
> > self bindKeyCombination: $+ command mac | $+ ctrl win | $+ ctrl unix
> >   toAction: [ self increaseFontSize ].
> >
> > that only works for the numeric '+'.
> > Is that supposed to be the case? The problem is that it forces me to know about the keyboard layout to define shortcuts.
>
>
> So you mean that in order to make + in your +/= key you must press shift? And then (ctrl +) does not match (ctrl shift +)?
>
> Then I’d say it is a bug/unimplemented feature...
>
> Hmm, maybe shift only has to work as a modifier for alphanumeric characters...
>
> >
> > I stumbled across this too, I don't think it is supposed to work that way.
> >  
> >
> > Stephan
> >
> >
> >
> >
>

How is this a bug? The only + key that you can press with just ctrl is
the numeric one, otherwise it would clash with "$= ctrl".

But since that's how most applications behave, I would propose to
actually use "$= ctrl" for zooming in.

--
Peter

Reply | Threaded
Open this post in threaded view
|

Re: Keymapping, shift vs non-shift

Stephan Eggermont-3
On 14-12-15 12:38, Peter Uhnak wrote:
> But since that's how most applications behave, I would propose to
> actually use "$= ctrl" for zooming in.

That's an interesting bug. I notice Safari, FireFox and Chromium have
the bug. They explicitly state in the menu that the key combination is
ctrl-+, resp. cmd-+.

ctrl-= doesn't exist on a german keyboard (but ctrl-+ looks fine)

Stephan


Reply | Threaded
Open this post in threaded view
|

Re: Keymapping, shift vs non-shift

Guillermo Polito
In reply to this post by Peter Uhnak

On 14 dic 2015, at 12:38 p.m., Peter Uhnak <[hidden email]> wrote:

ve, I would propose to
actually use "$= ctrl" for zooming in.


But that is layout dependent :).