JSLover wrote:
yup...just went looking & found...C:\Windows\System32\wmploc.dll...
ResHacker...
Great find and neat little program. This little program definitely goes into my toolbox. The
wmploc.dll file was loaded with information. It was a pain in the butt but I updated my notes in the 1st post to reflect a bunch of new message parameters that I found. Thanks for the info!
JSLover wrote:
what do all your "RC=FAIL" comments mean?...what failed...how?
"RC" is my abbreviation for return code (ErrorLevel). "FAIL" is the standard AHK ErrorLevel returned when using
SendMessage and there was a problem. WMP received and responded correctly to the message so I'm not sure why there was a problem.
PostMessage works in these instances (Errorlevel is always(?) 0) so use it for these messages.
I try to use
SendMessage whenever possible because 1) you can check the return code and 2) the script never gets ahead of itself (usually) because it always waits for a response before continuing.
Goyyah wrote:
Brute Force?
I just wrote a script that sent a sequence of messages to WMP, one at a time, and I just observed what happened. Some of the stuff was obvious. The other stuff was a little tricky.
Goyyah wrote:
I think Spy++ should also work...
As I noted in the original post I used
WinSpector Spy but couldn't get WMP to give up a single usable message. I don't have
Spy++ but I may have to track it down so that I can use it in the future. I've gotten mixed reviews on the program but I just may have to bite the bullet.
Just out of curiosity, did you try
Spy++ on Windows Media Player 10?
Thanks to everyone for your feedback. I appreciate it!
I'm still looking for more formal/complete documentation. If anyone has it, please pass it along.