Correction, it is even weirder than that. It is as if ALT+L was somehow turning the Library core on/off.
From my observation, it is as if there was this "hidden" state:
enabled = false // "media library engine" for lack of a better term; when false, this causes the empty freezing media library window
ml_open = false // the UI visibility
// when you focus winamp and press Alt+L
function altL() {
if (ml_open) {
ml_open = false
enabled = false
} else {
ml_open = true
enabled = true
}
}
// when you hit the global AltGr+L or Ctrl+Alt+L
function altGrL() {
if (ml_open) {
ml_open = false
} else {
ml_open = true
}
}
Now I hope you see where I am getting with it. In short, it is possible to make it such that "enabled" is false, while "ml_open" is true.
Basically, when I first open Media Library with Alt+L and then close it with AltGr+L, then I can use it as expected, but I can never close ML with Alt+L, this breaks it until I open it again with Alt+L.
// example state machine
[ enabled, ml_open ]
[ false, false ] // engine disabled, UI closed
altL() -> [ true, true ] // engine enabled, UI visible
altL() -> [ false, false ] // engine disabled, UI closed
altGrL() -> [ false, true ] // engine disabled, UI visible <- frozen empty window
altGrL() -> [ false, false ] // engine disabled, UI closed
altL() -> [ true, true ] // engine enabled, UI visible
altGrL() -> [ true, false ] // engine enabled, UI closed <- opened with altL, closed with altGrL keeps it working
altGrL() -> [ true, true ] // engine enabled, UI visible <- working window
altL() -> [ false, false ] // engine disabled, UI closed