MobileRead Forums - View Single Post - FBInk: A small tool/library to print crap on your screen!

Acorn · 01-21-2021, 09:39 AM

Thanks that's perfect!

If I'm going the admittedly hacky route of stealing input and drawing my app over the top of everything, am I going to have problems with nickel trying to draw things over the top of me? If so is there a reasonable way to prevent this? Also, is there a way to get everything back onto the screen when my application is closed?

Is it a matter of stopping nickel and then starting it again when the app is closed?

I see kobo dashboard does this..

Code:

# Flush the disks: might help avoid damaging nickel's DB...
sync
# Stop kobo software because it's running
killall nickel hindenburg sickel fickel fmon > /dev/null 2>&1

Don't see anything that would then try and start nickel again.. I guess the user is just expected to power cycle the device.. that's an easy solution I suppose

Also, I've been having a bit of a play with using touch input.. and I was wondering if using libinput would be the proper way to do it, rather than the low level hacking that Kobo-Input-Python does.. looks like it would make it quite easy to have plug and play usb input devices if you were so inclined too..

Would libinput be hard to build for the kobo? Maybe it could be included in the almighty Stuff bundle?

Might be a total red herring, I'm not sure if it would necessarily understand the kobo's touch screen, not fully clear on how nix works with input devices / drivers etc.

Cheers!

01-21-2021, 09:39 AM	#199
Acorn Connoisseur Posts: 56 Karma: 74 Join Date: Oct 2010 Device: Kindle 3	Thanks that's perfect! If I'm going the admittedly hacky route of stealing input and drawing my app over the top of everything, am I going to have problems with nickel trying to draw things over the top of me? If so is there a reasonable way to prevent this? Also, is there a way to get everything back onto the screen when my application is closed? Is it a matter of stopping nickel and then starting it again when the app is closed? I see kobo dashboard does this.. Code: # Flush the disks: might help avoid damaging nickel's DB... sync # Stop kobo software because it's running killall nickel hindenburg sickel fickel fmon > /dev/null 2>&1 Don't see anything that would then try and start nickel again.. I guess the user is just expected to power cycle the device.. that's an easy solution I suppose Also, I've been having a bit of a play with using touch input.. and I was wondering if using libinput would be the proper way to do it, rather than the low level hacking that Kobo-Input-Python does.. looks like it would make it quite easy to have plug and play usb input devices if you were so inclined too.. Would libinput be hard to build for the kobo? Maybe it could be included in the almighty Stuff bundle? Might be a total red herring, I'm not sure if it would necessarily understand the kobo's touch screen, not fully clear on how nix works with input devices / drivers etc. Cheers! Last edited by Acorn; 01-21-2021 at 10:00 AM.