Quote:
Originally Posted by NiLuJe
Fair warning if your device is already is USBNet mode: Nickel will happily switch to the "Connected" black screen, but will crash and burn a horrible death on *exiting* it ^^.
(Perfectly safe in a stock USBMS state, though).
|
Thanks for the heads up!
So, made some progress.. have a chessboard being drawn using calls to fbink_cls for the squares, and fbink_print_raw_data for the pieces extracted from a PNG sprite sheet using PIL.
Also have basic touch input working with libevdev. Didn't realise it even had the ability to "grab" the input built in! Sweet.
What's the deal when it comes to best practice drawing stuff to screen. I'm guessing that ideally you want to only draw stuff to screen that has changed to avoid unnecessary flickering, and that fbink doesn't do anything clever in this regard? Does fbink_cls do something special at a hardware level? Is it more efficient than printing an equivalent image for example?