Originally Posted by DJ Egg
View Post
I just ran some tests with recent development files from my skin (see screenshot) and must admit that the culprit was hiding somewhere else.
In the upcoming version 2.3 of my skin there will be a new feature called Playlist Editor2, which will contain some useful options regarding editing playlists:
And within the script for that particular component I found a bug, which never made problems while running the skin. I just put a setDelay(); within a timer and hitting the OPTIMIZE button caused that whole mayhem. So we're good now.

Comment