Oh, idea... Or maybe this wouldn't be efficient. (no, I haven't tried any other stuff, my code is at home, and I'm at work, I'm just trying to build up as many ideas as possible to try in one big session :) ) What do you guys think?
I could move my primary timer over to timer 1, then have the routine simply clear the carry bit, clock the shift re, and then check the carry bit every iteration... But when I'm getting ready for that portion of code, I could init timer 0, and let the input kick timer 0 on. Timer 0 would then simply set the carry bit and RETI... I suppose I'd have to set the timer 0 on a VERY large cycle time, then initialize it just as the program portion is starting, to make sure it doesn't go off...
Any thoughts on this theory? would that be worth trying? And if so, should I have the program pause for a few cycles after clocking the chip, before checking tha carry bit? I guess I can play around with that (trial and error kinda thing). But is this a retarded idea altogether?