class @beta Efl.Input.Key extends Efl.Object implements Efl.Input.Event, Efl.Input.State { [[Represents a single key event from a keyboard or similar device. ]] ... }
Description
Details
- Differential Revisions
- D9149: efl_input_key: declare stable
- Commits
- D9264 / rEFL1c8f6132af0e: declare a few classes stable
D9141 / rEFL6b8900d4fc69: efl_input_key: compose -> compose_string
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | None | T7562 efl.input.interface | ||
Resolved | None | T7964 Efl.Input.Key | ||
Resolved | None | T7967 Efl.Input.Event | ||
Resolved | bu5hm4n | T7968 Efl.Input.State | ||
Resolved | None | T7969 Efl.Input.Device | ||
Resolved | None | T7970 Efl.Input.Device_Type | ||
Invalid | None | T7971 Efl.Input.Lock | ||
Invalid | None | T7972 Efl.Input.Modifier |
I see nothing wrong, but I cannot be sure because the docs are absolutely horrible. What is the difference between key and key_name? What is this composition? I would love to see examples.
This is basically copied out of X11 terminology since that's what EFL was originally written around. key is the name of the key that was pressed (determined after processing) while key_name is the raw name of the key that was pressed. compose is compose keys...you know...where you press your compose key and get those funny little marks that non-english languages need.
Sorry, I am not familiar with X11 so I do not see the difference between a key name and a raw key name... example?
I know that I need to press two keys to get an ó: first ´ and then o. What events does this sequence generate in EFL? and what is the string and the compose_string for these events?
Um...I forget off the top of my head but I think it's like for keyboard remapping where you might e.g., press caps lock but it generates control.
! In T7964#137337, @segfaultxavi wrote:
I know that I need to press two keys to get an ó: first ´ and then o. What events does this sequence generate in EFL? and what is the string and the compose_string for these events?
Would have to check, as a member of the superior language club I don't need to use compose key myself. Should be easy to set a breakpoint on something that processes key events and look.
Well, OK. This seems general enough (by the sheer amount of properties it has) to future-proof us for the time being. It only needs docs.
P.S. I LOL in the general direction of your context-dependent, incredibly ambiguous, unpronounceable unless you heard it first, superior language.