-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Screensaver: add option to require a gesture after resume #9316
Conversation
ab5b6b1
to
991b67b
Compare
How is this meant to work exactly? I toggled this on, but there was no prompt to set the gesture. |
There could be at least a message if/that no gesture is yet configured. |
Thanks @poire-z. FWIW I have three new devices with Koreader, and none of them showed a message when I enabled the screensaver gesture. I had a bit of a hunt but couldn't find anything obvious. I could find the Gesture manager, but nowhere obvious to add the correct gesture. Which menu item am I looking for exactly? |
I don't think anything happens when you set the "Exit screensaver gesture" gesture, but if you enable the Screensaver setting that requires the gesture to exit, you definitely get a popup saying that says "the gesture is unset, tap to exit" (or something to that effect) on top of your screensaver when the gesture is unset. As for the gesture itself, it's in the Gesture manager, which is in [Gear] > Taps and gestures > Gesture manager; at which point you choose which kind of gesture you want to use for it, and find "Exit screensaver" in the list (which, yeah, is kinda backwards if you're not used to the gesture manager framework ;)).. |
Thanks @NiLuJe. I'm not entirely sure we're talking about the same thing, so I'll be totally explicit with which steps I took. I tried to enable the screensaver gesture with the following: This does not create a popup. I did found where to set the gesture itself (thank you!). However, I can't get this to work. I checked I then realised that the file browser seems to have a different set of gestures, so I set the |
When I wrote There could be at least a message if/that no gesture is yet configured, I meant it would be nice if it did - but it currently does not. So don't worry if you don't see that not implemented popup, no one does :) And yes, one needs to configure the gesture in both reader and filemanager. Your procedure looks correct, and it should work. |
Thank @poire-z. I understand now . I see @NiLuJe did a sneaky edit to clarify as well 😂
Yes, the gesture (down, up) works when I assign it to another action. Just not for
I tested the following, which worked:
I tested a different multiswipe gesture (up, right), and this also failed. |
If you were on latest nightly (good!), are using Pocketbooks (3 of them ! a bit less good :), try this morning nightly. Multiswipes were broken between these 2 nightlies, #9444. |
Sorry, I'm just running the latest stable on (3) Kobo Claras. Also, multiswipe does seem to work for other actions, just not |
It also works for me on a Forma, which should have a similar panel, although I had to ditch my halved swipe gesture intervals, because 450ms was way too short for a four direction swipe ;p. |
I just tested on my Kobo H2O, and this works fine. This was an old installation originally from six years ago (!). This is just not working on the Kobo Claras, with a recent (~2 month) koreader install. Is there any other information I could provide? I wonder if it might be something to do with the different configs? I can try and compare them perhaps? |
Verbose debug logs of you trying to unlock the screen would help, yeah ;). (Verbose debug flags are in [Tools] > More tools > Developer tools) |
Rather some kind of "child lock" than real secure protection, which we can't ensure anyway.
See #5970 (comment) and follow ups.
Related feature requests: #5970 #9270 #2255.
Tested on the emulator and my Kobo.
Somehow, by luck because I didn't need to look at all that, this works/happens
Rewording suggestions for the 4 strings welcome: exit/leave screensaver ? specific/owner/user gesture ? Waiting/Something else... ? I don't feel "Input/draw gesture" is to be used, as the gesture can be long-press in corner which wouldn't really be drawing.
This change is