Skip to content

InputDialog: Make sure keyboard_visible is never nil'ed#12994

Merged
Frenzie merged 2 commits into
koreader:masterfrom
NiLuJe:inputtext-iskyeboardvisible-notnil
Jan 3, 2025
Merged

InputDialog: Make sure keyboard_visible is never nil'ed#12994
Frenzie merged 2 commits into
koreader:masterfrom
NiLuJe:inputtext-iskyeboardvisible-notnil

Conversation

@NiLuJe

@NiLuJe NiLuJe commented Jan 3, 2025

Copy link
Copy Markdown
Member

InputText:isKeyboardVisible could return nil when the keyboard was
already gone, which cleared the instance variable, meaning we end up
with the static class default instead, which is true...


This change is Reviewable

NiLuJe added 2 commits January 3, 2025 03:58
InputText:isKeyboardVisible could return nil when the keyboard was
already gone, which cleared the instance variable, meaning we end up
with the static class default instead, which is true...
@NiLuJe

NiLuJe commented Jan 3, 2025

Copy link
Copy Markdown
Member Author

Re: #12951

(Completely untested, there might be gnarly codepaths relying on the previously buggy inheritance...)

@Commodore64user Commodore64user left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tested on K4, works fine now. Haven't encountered issues elsewhere but only time will tell...

@NiLuJe

NiLuJe commented Jan 3, 2025

Copy link
Copy Markdown
Member Author

Thanks! I'm hoping that since nil is falsy and we only ever really cared about this in the case where a VK was actually instantiated, there shouldn't be too much potential fallout, buuut (famous last words ;)).

@Frenzie Frenzie added this to the 2025.01 milestone Jan 3, 2025
@Frenzie Frenzie merged commit 53f8c2a into koreader:master Jan 3, 2025
0xstillb pushed a commit to 0xstillb/koreader-thai that referenced this pull request May 9, 2026
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.

3 participants