PocketMatrix

Johan, that's exactly what I am doing.

But that's where/why my problem arise:
Because of the different order in which the stylus events are fired, on my stationary PC I do NOT get a StylusMove: because the StylusUp comes before the StylusMove, the stylus-down-flag has already be reset.

But on my ipaq (2210) the StylusMove directly follows the StylusDown, so the flag is still set and I receive/process a StylusMove (which I do not want if it is only a tap on the screen on one location).

The solution will probably be that I continuously register the coords in the StylusDown and StylusMove and check in the StylusMove if the new coords are really different from the registered ones. Only then I will consider this as a real StylusMove.

But what I don't understand is why a StylusMove is generated in the first place when I just tap on my PPC screen???

Note that on a stationary PC, you will get StylusMove messages whether you click or not. In other words, just moving the mouse around the app's window will result in StylusMove messages. Maybe this is the source of your confusion, at least as far as a stationary PC goes.

I know this because I just took the minimal sample and put MessageBox's in StylusMove, StylusDown and StylusUp. Sure enough, just moving the mouse over the window results in a boatlod of StylusMove's, but no StylusDown or StylusUp's, as you would expect, until I click.

ppcStudios: Unfortunately I am at work now, so I can't send or attach my project yet. I will do this tonight.
But the timing/flushing of buffers seems fine to me: just take a look at the timing info at the start of each line: they seem to be in the right order.

Thanx for the suggested solutions, I will implement these to get things working right again. I obvious have to change some things to get these events working the way I expect them (on all platforms).

Note that my main question remains why on the PocketPC the extra, not expected StylusMove event occurs when only tapping the screen.
But maybe it is what InexorableTash mentioned: Windows just throws all kinds of messages at you which and when you just don't expect it...