Post #2221455
2026-03-17 05:33 UTC
Replies (2)
-
@_the_cloud@mastodon.social 2026-03-17 05:37
@kalleboo@bitbang.social @theirongiant@hachyderm.io That could be it. My really, really dim memory is that the WindowShade INIT sets some region of the window to nil (or an empty region) and it would make sense that they stash the old region somewhere else while it's collapsed.
-
@theirongiant@hachyderm.io 2026-03-17 22:38
@kalleboo@bitbang.social @_the_cloud@mastodon.social - Here's what I've been discovering: if I double-click too quickly on the FatBits window, it crashes. If I double-click slower, it doesn't. WindowShade reacts to two clicks that are <500ms apart. Any slower, and it's just two separate clicks. Between 500-333ms, the FatBits window behaves normally and the program does not crash. If I double-click faster than around 333ms (around 1/3 second), the app crashes consistently.