Were you getting valid data on your glcd reads? or just always getting 0 or FF?
i.e. does line() work properly by overstriking the existing pixels?
Yes I was.
Yes it does.
Interesting... I'm kind of surprised.
hmm. I wonder if it is glcd specific and some glcd modules disable the bus in s/w vs hardware
(which might make the validity stretch beyond the E dropping a while longer)
or maybe they use R/W to determine when to drive the bus and not actually gate it with E.
The samsung ks0107/8 spec and all of the glcd specs I have show
the read data only being valid while E is high.
They may not have really implemented it that way but
its probably best/safest to read the data when E is high - That's what I do in the glcd library.