v0.4.1

A single fix, on top of v0.4.0 from earlier today.

The first stroke after returning to the app was silently swallowed

Click away to another application, come back, and draw — the first thing you drew was lost, while the second stroke and every one after it drew normally. Wintab only; the Avalonia Pointer path was never affected.

Wintab delivers packets to whichever context is on top of the driver's overlap order, and losing focus drops ours down it with nothing to put it back. The repair is WTEnable followed by WTOverlap, matching what Qt does on window activation — which is why Krita does not have this bug and Clip Studio Paint, on Wintab, does.

That repair lives in WinPenKit and shipped in its release/v0.4.0. What this release adds is the one thing only the application can do: a Wintab context is bound to a hidden message window that never receives WM_ACTIVATE, so the app has to say when it is back.

What's Changed

• Tell the pen session when the window is activated by @TheSevenPens in #30

Full Changelog: v0.4.0...v0.4.1