Quote:
Originally Posted by brucelee
Thought about it a bit more.
I implemented this because I have a case for the reader and the device is set to turn off after 1 hour. So most of the time I just close the case cover and let it be. The stand by mode will turn off the light after 5 minutes and return to its initial state really fast when any input is received. So I'm not worried about unwanted input that may occur.
Now there's the situation you pointed out which seems to be necessary for those users not having a case for the reader. Well, a slide unlocker would be useful indeed but the problem is that it won't block all the buttons. The home button is system assigned and I can't override it through the app. That's because the event never reaches the app. Sooo basically, this isn't quite a real lock feature since pressing the home button still "unlocks" the device. I suppose the chances are not in favor of the button being randomly pressed but it can still happen and screw things around.
|
In principle, it is sufficient to block the screen. The buttons are pressed tightly.
Yes, and the current state is not clear - whether the device in stand by mode, or already off. On the screen in any case, cover and once again touching the screen to verify this. A bit uncomfortable.