Minor update, I'm not sure if this is a generic issue or something specific to my device, but I noticed that sometimes no matter where you touch, it sometimes registers as touching x=0 y=0
Which, when answering flashcards, would result in the wrong answer... so I made a workaround for regions to start at x=1 y=1 so x=0/y=0 is ignored. Also added a condition that the region must be hit twice in succession to be valid (a single touch usually reports 3-5 coordinate pairs for me so I'm requiring two for now).
Hopefully this will get rid of misdetections.
TODO:
- implement text/csv source deck, to be rendered by fbink's new truetype handling
- finish the half-done javascript flashcard generator anyhow
- re-factor the script to also allow standalone mode
- optimize deck logic, perhaps implement in C
|