.getCount() is cumulative. You shouldn't be missing anything regardless of when you read it. You could poll the twist once a second and it shouldn't miss anything; the ATtiny will just sit there and happily track the encoder.That seems to keep the interrupts from firing off repeatedly, but It doesn't give you correct updated counts (misses many counts).
Button presses are different. If the user presses the button once, and you polled 1s later, you'd see it. If the user presses the button twice and you polled 1s later, you'd see only the indication of the one press.
Yep. I can do that. I'm also planning on implementing a proper state machine so there's less toggling of the INT pin.Maybe separate clearing encoder interrupts and button Interrupts. Maybe do a twist.ClrEncInterrupts() and twist.ClrButtonInterrupts() by themselves?
Glad to hear you got it (mostly) working! Let me know if anything else pops up.