Replies: 6 comments 1 reply
-
I don't see any issues with your setup, it's just that you have So kanata is working as intended. |
Beta Was this translation helpful? Give feedback.
-
Hi,
The issue is, I have another key (called This key ( I hope it is clearer now. I do think this should be labelled as a bug and not just a question, but I might have to further explain myself as the matter is not common for most english-speaking devs (few-to-no diacritics in english, and classical deadkeys are often enough). |
Beta Was this translation helpful? Give feedback.
-
Thanks for the reply @Ced-C. I'll keep it marked as a question for now since it's still unclear to me how this should be fixed within kanata. There is no concept of When I think about in what ways it looks different, the main thing I can think of is the time gap between the press and release events. Perhaps since the release of the A potential workaround might be to have the tap key be
Or alternatively, use something like below to make the press and release even further apart - in this example 20ms.
|
Beta Was this translation helpful? Give feedback.
-
Thanks for your swift answer. The first suggestion did not seem to work, but the 2nd one did! Should I close this issue now ? or do we want to document that somewhere ? Let me know! Édit : timing becomes critical and seed to lead to some inversions, I’ll continue to test and play with the timing to see if the behaviour can be improved. Will not close the issue and let you know how it goes if it is ok with you. |
Beta Was this translation helpful? Give feedback.
-
Sure thing, once we have more info let's add it to the documentation. I wonder if it might be worth opening a bug, or see if there is an existing one, against xkb - or whatever project handles this functionality, I don't have any links on hand. To me it seems undesirable to have this timing-dependent behaviour, when all that matters is the key press/event sequence. |
Beta Was this translation helpful? Give feedback.
-
Agreed, depending on the timing the exact same sequence at approx the same frequency can give a different result which is not what one would want to write. |
Beta Was this translation helpful? Give feedback.
-
Requirements
Describe the bug
Hi,
Thanks for writing Kanata, great app really except for this annoying bug.
Like many French using a custom layout, I am using an ISO_LEVEL_3 latch key (let's call it il3 key) to access some diacritic letters (
é è ê ù â ç ñ
etc.).for instance, typing
il3
+ (then)e
→(gives)è
, similarly;il3
+u
→ù
The issue is, that I am not able to take full advantage of kanata because if I tape il3 key then any key that is used as a mod-tap or a layer-tap, the il3 key is ignored.
u
is not modified by kanata:il3
+u
→ù
u
is a mod-tap or a layer-tap:il3
+u
→u
a workaround is to maintain the
il3
key hold wile typing theu
key, this provides the expectedù
, but it is really strange to type like that —especially when one is touch-typing.Relevant kanata config
To Reproduce
il3
+␣
→’
il3
+␣
→␣
Expected behavior
il3
+␣
→’
Kanata version
1.4
Debug logs
Activating the debug mod and doing
il3
+␣
:Operating system
Linux, Ubuntu 22.04, Gnome-42 Wayland
Additional context
I can make additional test if required. I am not sure how trivial this is…
Maybe something to do with action on released key rather than pressed ?
Beta Was this translation helpful? Give feedback.
All reactions