koreader

Commit Graph

Author	SHA1	Message	Date
NiLuJe	53c0a65a5b	ExternalKeyboard: Don't spam the "Keyboard connected" InfoMessage Only show it for the first keyboard	2 years ago
NiLuJe	5b6d2ab66f	ExternalKeyboard: Workaround bad interaction with coverbrowser when enabled on startup	2 years ago
NiLuJe	02020176a9	ExternalKeyboard: Only disable OTG on exit We currently did so on plugin destruction, which was a bit overkill/annoying, as plugin instances are torn down on view changes (i.e., when FileManager/ReaderUI are torn down) ;).	2 years ago
NiLuJe	9863a9c0bb	ExternalKeyboard: Use the evdev number passed along by base to avoid sweeping the full list of input devices This required some... creative thinking to avoid complexifying common Input/UIManager codepaths ;p.	2 years ago
Borys Lykah	9b2201a438	Initial hotpluggable keyboard handling (#9540 ) * Added a new plugin external-keyboard. It listens to USB events. When keyboard is plugged in or plugged out, it updates device and input configuration accordingly. * Added new fake events UsbDevicePlugIn and UsbDevicePlugOut that are emitted when a device is connected to a book reader that plays the role of USB host. The usage of the existing events UsbPlugIn and UsbPlugOut has not changed - they are used when a reader is connected to a host. The koreader-base has a related PR for those events. * Did a small refactoring of initialization for the modules FocusManager and InputText. They check device keyboard capabilities on their when the module is first loaded and store it. Some of the initialization code has been extracted into functions, so that we can re-initialize them when keyboard is (dis)connected. * Initial implementation centered around text input, and tested with USB keyboards on devices with OTG support. * Said OTG shenanigans are so far supported on devices with debugfs & the chipidea driver, or sunxi devices.	2 years ago

5 Commits (8cba303b96f52b768bea5b21a35b3cba46b14895)