-
Notifications
You must be signed in to change notification settings - Fork 3
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
create a toonstore app #102
Comments
|
Alternative idea: a toon app that just clears out as much as possible of the screen and tells us what rectangle on fb0 is ours. Then only handle touch for that area. Toon's Home button (or, well, its touch area) appears to be 86 wide, 55 tall, so either we get 800x(480-55=425), or we get 800x480 minus that 86x55 square. |
as far as I can tell, we cannot spawn processes from QML, but writing
|
Braindump:
|
Even though we are not a QML app like other toonstore apps, there's no reason we could not be in their 'store' (all of which is free). My current thinking is a Voorkant button that opens a simple confirmation dialogue, that explains that returning to Toon will take a few minutes.
As for implementation, I do not know if QML apps can execute things, but I do know they can write files, so one approach might be that some voorkant-launcher-daemon is running, waiting for the appearance of some file somewhere, and then it kills
qt-gui
and startsvoorkant-lvgl
.For bonus points (I've been pondering this for a while without a sensible outcome so far), find a way to suspend
qt-gui
-without- it getting delivered 500 touch events when it resumes, so we can cheaply switch back and forth.chvt
does not appear to be the way, it's in the wrong layer.The text was updated successfully, but these errors were encountered: