Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A few questions #886

Open
WubTheGame opened this issue Jan 24, 2025 · 5 comments
Open

A few questions #886

WubTheGame opened this issue Jan 24, 2025 · 5 comments

Comments

@WubTheGame
Copy link

WubTheGame commented Jan 24, 2025

https://github.com/Julow/Unexpected-Keyboard/blob/master/doc/Possible-key-values.md

-As referenced here, I'm not clear on what exactly is a "built-in key value". What I can say is I've not been able to create a key that sends Ctrl Backspace (or Delete). My meaning is to have such keys that can input the modified version of whatever the following key is, without keeping the modifier itself active. So Ctrl Backspace would instantly press Ctrl, Backspace, and release Ctrl.

Use case example: If I've made a typo early in a word, it would be faster to delete and rewrite it entirely than press Ctrl, then arrows, and pick out what needs fixing. That said, I certainly wouldn't mind putting more such keys in like Ctrl arrow keys. And then it'd be great to be able to choose a display "name" for the key, like "C[backspace icon]". Or even a different color. I recognize though that's another thing on its own at that point.

If this isn't possible, can that be changed? I'm no Android dev but if it were fairly easy to implement I might go for it. But if it's outside the control of the keyboard, darn.

-I'm puzzled by the purpose of the "Compose" key? I see it darkening half the characters, but for what?

-Is there a place I can get the exact base layout for the bottom row to modify it a bit? I know how to not get a duplicate, but how do I "replicate" it first?

-Very advanced thing to implement I'll bet (or just too heavy for this light a keyboard), so I'm not expecting anything, but it'd be cool to have context sensitivity for keys. Like if I want a key to show up somewhere specifically if a certain other key(s) has just been pressed, I can specify that in the config. And/or per app keys, so a key will be one thing in one app and a different thing in another. I do understand privacy may become a concern for some if such a thing were implemented.

This one I'm really just putting on the table with a confession that I don't actually have practically any need or use for this right now (at least the per app part). The power user in me likes options. Low priority but a cool idea. As for the first part, I could see myself setting keys around (as in corners and edges of the M key) "M" to "'d", "'ll" (mind the single quote in there), etc, if I've just pressed "I" to make it that little bit faster to type "I'd" or "I'll".

I guess I'm basically asking for a smart keyboard in this? XP

-Lastly, I'd like to be able to adjust how much emphasis needs to be placed in the corner of a key to output its corner key. I find a tendency to output a corner key from a slight enough slide in that direction that it shouldn't apply the corner key. I've been using this keyboard for probably weeks now and this is noticeable.

Thank you in advance.

@Spike-from-NH
Copy link
Contributor

① Syntax is emerging to let you code things like Ctrl and even define the key's legend. It would use the same structure as the extensions at the bottom of possible-key-values.
② The Compose key lets you press two keys to generate one key not on the simple keyboard. For example, Compose-1-3 generates ⅓. When you press Compose, only the keys it's meaningful to type first are lit. 1 is lit. If you press 1, then the 3 key turns to ⅓. It's all a prompting system.
③ The current definition of the bottom row is at [https://github.com/Julow/Unexpected-Keyboard/res/xml/bottom_row.xml].
④ The bottom of possible-key-values already shows a way to make a gesture output a string. If there no apostrophes, you don't have to get this fancy; my layout has nw="the ".
⑤ I think a way to put conditionality into a custom layout is beyond the scope of a "lightweight" keyboard project.
⑥ It's not a matter of how much emphasis you put in the corner of a key, but of the distance the finger travels, and this is "Swiping distance" in the Settings.

@WubTheGame
Copy link
Author

Can I change the Compose layout (or any other)? I have no use for it and would like to repurpose it for writing short words and phrases as keys to avoid typos and be faster.

@Spike-from-NH
Copy link
Contributor

To avoid Compose being automatically assigned to a key, use Gear logo > Add keys to the keyboard and uncheck it. To put it somewhere else, add to the preferred key in your custom layout something like nw="compose".

@WubTheGame
Copy link
Author

You misunderstand. I'm not looking to (re)move it, but to change its layout. Change what keys appear and how they function with the Compose key.

@Spike-from-NH
Copy link
Contributor

I did misunderstand. Although the Compose key is wonderfully table-driven, so far the table is not user-editable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants