Hi SilverEagle,
thanks for your suggestion - it might indeed be a good idea to add some code that checks for tracks that get queued twice in error - I added this suggestion to my todo list.
The little topleft message box is only there during the development stage - I plan to implement some text that is much more "in the way", so even a "lubricated" party guest can't overlook it: in fact I plan to temporarily overwrite the entire player section with the message. However, I'm not fond of the extra click that the use of the MessageMode function requires in this case. Ideally, I want the player section to revert back to it's original state after a little time has elapsed, as the player is the place where the user expects dynamic data to appear. I really appreciate your suggestion to look into Tick() instead - I wasn't aware that it is being used permanently, but judging from the function name it probably is the function that makes the skin tick
... Guess it's about time to look into the timing aspects of your skin as well to understand it better.
Using a counter for timing purposes of course has the drawback that it is dependant on the processor speed of the PC, so it might be a good idea to make this a configurable value as well. However, I'm afraid to add even more features to the configuration screen, as complex config screens often make potential users shy away from a piece of software in my experience. I can easily test the impact of the performance on the timing though, as my live jukebox is a nettop powered by Intel Atom N330 with 1.6GHz and only 2GB RAM, while my development machine is an Intel i7 with lots of RAM.
Cheers
Joachim
