|
|
|
|
|
|
by thedoctor_o
1589 days ago
|
|
|
The complication is that what's been leaked just can't be used by anything trying to be legit because it was not released in any official manner & so it's license isn't at all clarified even though it's a pre-release copy from the AOL era which some would say it's abandonware. Plenty saw the publicly posted screenshots of partial headers from the source files on twitter that were being used to prove it was a real leak which I unfortunately was greeted to on opening a DM (which I wasn't happy about) otherwise everything else gleaned was taken from others observations at the time. With the clear demise of 'classic' Winamp with the whole 'set the tone' & seemingly nft related crap the new lot are now going for, what was leaked still equates to what's gone to the new owners (which was one of my pre-sale tasks) so it's into the messy state of who has recourse against it being leaked. As for the issue, I don't remember there being anything specific that is in place to make it intentionally block system closing unless it's taking too long &/or it's crashing. I don't have the Winamp core handling that aspect of the running process with the current preview build (& the beta builds barely let the Winamp core do anything with it being able to run without it with some missing features) so the best way to find out if it behaves would be to try it out as a portable install so it doesn't mess with your existing Winamp install. -dro |
|
|
It will never close (unless you click "shut down anyway"). Maybe I'll dig into that some day - after a quick google, maybe it just doesn't honor the window messages to close the program.
I use a portable install anyway, so that hopefully won't be an issue (if I ever get around to testing)!