[plugin dev] Input performance covers_fullscreen from reader view

oleasteo · Today, 10:40 AM

I'm working on a lock screen plugin.

It uses a ButtonTable nested inside a FrameContainer.

Now, if I send my device to sleep and wake up, the performance differs heavily depending on the device state (file browser vs reader) and screensaver type:
- If screensaver is anything other than "Leave screen as-is" and I sent the device to sleep from an open book (reader state), the input performance of the buttons is very sluggish.
- If screensaver is "Leave screen as-is" or I sent the device to sleep from the file browser view, the input performance is perfect.

I've tried this without any screen updates from my code – aside of the ButtonTable's own ones.

As it's my first plugin and my experiences with KOReader are limited, I'm stuck and don't know how to debug further. Any help is appreciated.

oleasteo · Today, 02:20 PM

I think I've found the culprit: Disable double tap solves the issue.
Now, it's always pleasantly snappy.

Is there anything I can do in the code to the same effect on my overlay widget? So that I wouldn't need to bother my users?

Today, 10:40 AM	#1
oleasteo Junior Member Posts: 2 Karma: 10 Join Date: Oct 2025 Device: Kindle Oasis (10. Gen)	[plugin dev] Input performance covers_fullscreen from reader view I'm working on a lock screen plugin. It uses a ButtonTable nested inside a FrameContainer. Now, if I send my device to sleep and wake up, the performance differs heavily depending on the device state (file browser vs reader) and screensaver type: - If screensaver is anything other than "Leave screen as-is" and I sent the device to sleep from an open book (reader state), the input performance of the buttons is very sluggish. - If screensaver is "Leave screen as-is" or I sent the device to sleep from the file browser view, the input performance is perfect. I've tried this without any screen updates from my code – aside of the ButtonTable's own ones. As it's my first plugin and my experiences with KOReader are limited, I'm stuck and don't know how to debug further. Any help is appreciated.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Conversion Input] Doc Input Libreoffice Plugin	sac	Plugins	11	03-15-2025 07:08 AM
[Conversion Input] Microsoft Doc Input Plugin	igi	Plugins	77	03-08-2025 04:04 AM
Reset /dev/input/event1	bitfreak	Kobo Developer's Corner	2	01-17-2024 01:06 PM
[FileType Plugin] LCPL Input Plugin	Leseratte_10	Plugins	1	10-06-2021 03:58 AM
[Input Plugin] DOCX Input	SauliusP.	Plugins	42	06-05-2013 04:01 AM

Today, 02:20 PM	#2
oleasteo Junior Member Posts: 2 Karma: 10 Join Date: Oct 2025 Device: Kindle Oasis (10. Gen)	I think I've found the culprit: Disable double tap solves the issue. Now, it's always pleasantly snappy. Is there anything I can do in the code to the same effect on my overlay widget? So that I wouldn't need to bother my users?