Oh, that means that Qt is cooked in a wrong way.
I believe that if alt modifiers were passed as accel arg - they would have
been working ok

вт, 24 сент. 2019 г. в 12:26, vitalije <[email protected]>:

>
>
> On Tuesday, September 24, 2019 at 11:12:52 AM UTC+2, gar wrote:
>>
>> Vitalije, thanks a lot!
>>
>> I encountered another interesting and odd behavior.
>> When language different from english is enabled - all <alt>-based
>> shortcuts dont work while <ctrl>-ones do.
>> This behaves the same both on win and lin.
>> Why can this be so?
>>
>> This is most likely Qt issue. While searching for hard-coded Plugins
> menu, I found that Ctrl-<key> are passed as accelerator argument to Qt,
> while others are passed just as '&' character inside label. Not sure, but
> it might be that '&' makes accelerator only the following byte in name,
> which won't work for non-ascii letters.
>
> Vitalije
>
>
>> Indeed you were right, it was hardcoded. The revision e74419f3
>>>> <https://github.com/leo-editor/leo-editor/commit/e74419f3b348567add9485553a1502833597c78e>
>>>> fixes this. If you update to latest revision in devel branch, and remove
>>>> '&' from plugins menu in your settings, it won't be bound to Alt-p.
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leo-editor/abce7794-dbb3-4169-abb8-2065f88521de%40googlegroups.com
> <https://groups.google.com/d/msgid/leo-editor/abce7794-dbb3-4169-abb8-2065f88521de%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVzsnQNG%2Bk054TLGyT0D0uYCXbUmhKKzc-cAYw79oM%3D-Vg%40mail.gmail.com.

Reply via email to