Skip to content

Conversation

@hius07
Copy link
Member

@hius07 hius07 commented Jun 11, 2024

Closes #11990.


This change is Reviewable

@NiLuJe
Copy link
Member

NiLuJe commented Jun 12, 2024

Not sure we if we really want to change the variable name (mainly for backwards compat, especially with 3rd-party plugins; otherwise I'd agree with you that the current name isn't great ;)) ;).

Good idea to clean this up, though, thanks!

@hius07
Copy link
Member Author

hius07 commented Jun 12, 2024

backwards compat, especially with 3rd-party plugins

They would get the main (letters) layer of the keyboard instead of the numeric (symbol) layer, that's it, not a big issue I believe.

@Frenzie Frenzie added this to the 2024.06 milestone Jun 14, 2024
@hius07 hius07 merged commit ded709e into koreader:master Jun 15, 2024
@hius07 hius07 deleted the oninput branch June 15, 2024 06:54
@Biep
Copy link

Biep commented Jun 15, 2024

Just updated a minute ago, but still have issue #11990, so I suppose I still got a nightly from before the update. Will try again tomorrow.

@NiLuJe
Copy link
Member

NiLuJe commented Jun 15, 2024

Yup, the merge came juuuust after the nightly build (~6AM GMT) ;).

@Biep
Copy link

Biep commented Jun 15, 2024

Hmm.. I just now checked, and got "KOReader is up to date" - but the keyboard issue persists.

@benoit-pierre
Copy link
Member

It missed the deadline for the nightly, try tomorrow.

Commodore64user pushed a commit to Commodore64user/KOReader_fork that referenced this pull request Aug 2, 2024
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

Successfully merging this pull request may close these issues.

Keyboard in FM starts with special characters

6 participants