Mirek,

I was only thinking about declaring:

	virtual bool   PenDown(Point p, dword keyflags){ return false; }
	virtual bool   PenUp(Point p, dword keyflags){ return false; }
	virtual bool   PenMove(Point p, dword keyflags){ return false; }

and calling them directly like this

				switch(message) {
				case WM_POINTERDOWN:
					ClickActivateWnd();
					if(PenDown(Point(p), GetMouseFlags())) return 0L;
					break;
				case WM_POINTERUP:
					if(PenUp(Point(p), GetMouseFlags())) return 0L;
					break;
				case WM_POINTERUPDATE:
					if(PenMove(Point(p), GetMouseFlags())) return 0L;
					break;
				}
				break;

...and using the Pen -functions you made earlier.

EDIT: BTW: How did you think about handling barrel-button and other flags? After playing around with the pen, I have noticed that it is very difficult to click barrel and other buttons on the pen while keeping it steady. So, IMO, barrel should be just a flag to read when pen goes down/up or moves. Just like Shift/Ctrl/Alt, which are used and needed as modifiers similarly for pen and mouse.

Also, I feel PenMove + PenDown + PenUp make it easier to write code for the pen, instead of a single PenUpdate function.