Add option for (forcibly) stopping reMarkable UI while using remouse #98
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While using remarkable_mouse, the remarkable UI stays active, so I have to make sure I'm on an empty document and hope I don't accidentally click the button to show the pen panel.
I wanted to add an option to just disable the UI completely so the remarkable can be used as a pen-tab without thinking of what's on the screen at all.
I was hoping to send SIGSTOP and SIGCONT signals to the UI so I could just pause and resume it without risking losing any documents. This does work, however the remarkable must have some kind of watchdog process monitoring the UI, if it sits stopped for more than 30 seconds or so, the whole device reboots.
Instead, I went with the simpler option of just killing the UI completely. This closes open documents without saving them (unfortunately).
When done using remouse, it re-launches the remarkable UI. However, if the ssh connection was lost, or python exited non-gracefully, the UI won't be restarted and you must force-shutdown the remarkable by holding the power button.
This doesn't necessarily need to be merged, if the idea of force-closing documents is concerning. But figured I'd send it anyway and I'll be using it locally.
If I can work out which watchdog process is re-starting the device when using SIGSTOP, then maybe a more graceful pause/resume could be added.