==> please, consider to remove the FIX on tooltip added in V1.5.5, it makes WSH panel Mod unstable, may crashes (brutal with a black window named WSH Panel Mod that appear on freeze in the main foobar2000 window...

i don't really understand your 2nd point. like i said, it's custom code. it's what the author decided to do at the time. nothing more. there is no documentation other than the functions exposed in interfaces.txt and callbacks.txt. sometimes it hard to understand how it all works together which is why some samples have been bundled with the component. you may find they are not the most optimal way of doing things but it's a start.

remember you're not just limited to the built in functions. you can load activex objects to run external programs, manipulate files, access the internet, etc. that's all standard jscript which you can read about on MSDN.

This lists compilations by letter, with all non-letters (i.e. numbers or symbols) listed under "#". It groups compilations by series then album.

I want to make one change but I'm not sure about the code - currently it moves the prefix to the end (which is what I want). However, it still lists the compilation under the letter of the prefix. For example, "The Summer of Love" is listed under the letter T as "Summer of Love, the".

I want it to be listed under the letter S as "Summer of Love, the". Any help with changing my code to do this? Many thanks!

How can I get it to show the %tdrl% ONLY if it is different from the %date%? For example, if date and tdrl have the same value then %tdrl% should not be shown. But if they have a different value, then it should.

Also: you might want to read the documentation on title formatting (html included within foobar installfolder linked to on multiple occasions throughout the program's preferences) and trying to figure this out yourself before searching(!) And asking....

Not sure this has already be noticed by someone. I have switched recently to Windows 8 (x64) and kept my old foobar2000 config (from W7 x64), with all WSHPM scripts. They work as expected, except one thing. The mouse wheel doesn't work in WSH panels any more. More precisely, the delta of the on_mouse_wheel function is always 0.In other words, this script prints some zeroes in the log when the wheel is activated:

CODE

function on_mouse_wheel(delta) { fb.trace(delta);}

The wheel of my standard Microsoft mouse works correctly in all Windows programs and in Foobar2000, except in WSH panels.

The fact that the callback is called when the wheel is activated means that my mouse is correctly recognised, but the delta sent by the hardware is probably different than the delta of other mouses. I've read somewhere that old mouses reports a specific delta value (maybe 64 and -64, but I don't remember), but recent mouses are more precise and may report small deltas such as 1. That might be the case of my relatively recent mouse. I guess that WSHPM divides the delta by 64 (or whatever) to convert it to 1 or -1, and that may be the reason why the result is always 0. If it's the case, it it possible to fix that little bug in a forthcoming version? Thanks in advance.

Also, I have not installed the M$ Mouse and Keyboard Center because imo it is useless, but iirc it was installed on my old system. Could it be necessary?

According to the Device Manager control panel, my mouse did not need any driver. But I have installed the M$ Mouse and Keyboard Center anyway. (It's a pity btw. I don't need its features, and it launches 7 additional programs at Windows startup!) That was not sufficient to fix the problem. I had to go to "Mouse And Keyboard Center -> Basic Settings -> Identify programs that don't scroll correctly" and select Foobar2000. That fixed the problem, with a little drawback: now the non-WSH panels scroll more rapidly than before (approx 3 lines at a time instead of 1). Not a big deal.

Furthermore, I've noticed that after a reboot, when F2K is launched immediately, the WSH panels do not scroll. I have to wait at least one minute or so before they begin to work correctly. I suppose it's because the Mouse and Keyboard Center takes a long time to start.

IMO, it's not really a driver issue. The M&K Center is just an additional program to tune the mouse and keyboard behaviours with certain programs (mainly games), and should not be necessary for standard programs, such as F2K. So, IMO, there is still something to fix in WSHMP. Perhaps you should just test if the delta reported by the hardware is positive or negative, and convert it to 1 or -1 accordingly. Just my 2 cents.

The issue is solved, that's right, but the fix is not perfect, and should not be needed.Thanks anyway for the pointer.