The Mouse Thief: To prevent a "teleportation" bug when the window shatters, I’m using user32.dll to send a MOUSEEVENTF_LEFTUP signal. It literally prys the window out of your hand if you drag it too fast.
The Snapshot: It uses DwmGetWindowAttribute to find the exact frame bounds (ignoring those invisible Windows shadows) , takes a screen capture, and replaces the real window with a WPF PhysicsCanvas.
The Physics: Each shard is a Polygon shape with its own VelocityY (gravity) and RotationSpeed.

The Chaos (Warning: LOUD Audio): The GIF is silent, but I recorded a short demo with "m e m e" sound here: https://youtube.com/shorts/9bTcgtLpOXQ

The Project Page: If you want to break your own desktop, I put a free lite version on Itch. It also supports custom .wav modding if you want to swap the sounds for your own stuff. https://erza-lotus-arcane.itch.io/please-drag-me-gently

[–] netizen@programming.dev 0 points 2 weeks ago (2 children)

I remember having to program a trap for double-clicking buttons in an application.

Then I had to implement a penalty for triple-clicking.

Later, I converted it to a progressive incremental penalty.

[–] FunnyCoder@programming.dev 1 points 2 weeks ago

I’m actually surprised no one’s roasted my math in ShatterCanvas.xaml.cs yet—I’m basically faking the 'gravity' by just incrementing VelocityY every frame. It’s surprisingly lightweight for how many polygons are flying around.

[–] FunnyCoder@programming.dev 1 points 2 weeks ago

Incremental penalties are the way! I see you’re also a student of the 'Hostile UX' school of design. Shaking the window is basically the ultimate progression of button spam—once you exceed the velocity threshold, the UI simply quits on you. ψ(｀∇´)ψ