12-02-2010, 05:23 PM
Oh, you meant a move while it was being held down. If it's not sending you anything, then I don't think you ever got a press inside the widget. It would only send you something if you got the original press inside the widget. Otherwise it won't be tracking the widget and therefore it won't send anything.
That also kind of leads me to believe that maybe it's related to positions on the click. And that would also maybe explain what's happening, because it sees that first press as a release, so it thinks it's being RELEASED inside the button, and asks you to draw the unpressed image. After that, it gets into sync and works. Then, after a move, somehow, it's getting into that thinking it's pressed state again.
So maybe it's something like that, and it's just that I'm compensating for it unknowingly or something. I'll look at that.
That also kind of leads me to believe that maybe it's related to positions on the click. And that would also maybe explain what's happening, because it sees that first press as a release, so it thinks it's being RELEASED inside the button, and asks you to draw the unpressed image. After that, it gets into sync and works. Then, after a move, somehow, it's getting into that thinking it's pressed state again.
So maybe it's something like that, and it's just that I'm compensating for it unknowingly or something. I'll look at that.
Dean Roddey
Explorans limites defectum
Explorans limites defectum