andre@woesten.com 3dbfe2f82e BUGFIX: Finally fixed close flashing issue.
It must be called BEFORE WM_DESTROY because WM_DESTROY is emitted 
AFTER the childs and itself have been destroyed. In the resulting, 
short time interval (after destroy and before handling WM_DESTROY)
a new flashing can occur, because the Window Messaging System
seems to give the keyboard/mouse input to the next window. But
without waiting for the WM_DESTROY to be processed. That's why
we're directly doing it in WM_CLOSE now :-)
2008-11-05 23:19:48 +00:00
2008-11-03 12:53:04 +00:00
2008-03-18 09:06:19 +00:00
2008-10-21 19:46:17 +00:00
Description
a cross-platform, terminal-based music player, audio engine, metadata indexer, and server in c++
76 MiB
Languages
C++ 79.3%
Kotlin 12.5%
C 4.8%
CMake 1.3%
Shell 1%
Other 0.9%