To get some results, we should start with the absolute basics. Save off the file you have now somewhere so you don't lose it. Then erase all of the mappings you have in Resource.xml. Now let's start with just one command and get that working. Once that works, you'll know that you have the file in the right place, you have the correct syntax, etc. It gives you something you can return to as a working configuration.
I have Ctrl-D mapped to bring up DSP Studio because I use it so frequently. That's a nice safe place to start. Put in just this one Accelerator command:
<!-- DSP Studio -->
<Entry Key="Ctrl;D" Command="10016" Param="0" />
Save the file and restart MC. Once you get that working, we can move on to harder things. Keep reading below....
- MCC 30007 (Playlist): "int nPlaylistID". I guess it means "insert playlist ID". I tried the playlist name (with spaces) and it did not work. Is this ID something else? How do I refer to playlists nested in a group?
[/li][/list]
The Playlist ID is a unique identifying number for every playlist on your system. "int" is the C++ variable type for Integer (as opposed to floating point number). Getting that playlist ID isn't a built in function or property as you might expect it to be. It's there, but it's sort of hidden. If you make a new Smartlist, and put in a criteria of "Playlist is any " and select a playlist, you can see the Playlist ID. Once you set that criteria in the Edit Smartlist dialog, you can display the underlying "code". Press Import/Export at the lower left corner. You'll see something like: playlistid==536854610 . That big number is the Playlist ID. Playlist Groups have IDs too, but that really doesn't matter for your purposes. Just select the list you want, no matter how deeply nested it is, then use Import/Export to find it's Playlist ID number. Put that number into the Param and it will work.
- Global: the point is to make the accelerator operate even when MC runs in background? I always set it at "1", hoping this isn't a problem.
Honestly not sure how this works. I don't use Global on most of my keys.
Start small. Get one key working and verify it. Then add another key and verify that it works. This can require quite a bit of trial and error. I've found that some keys don't want to map at all. I think a very small number of keys might be either taken by the operating system, or deeply coded into MC. I'm not 100% sure; I just know some keys won't map. If you suspect you have a key that won't map, change it to something else and try again.
I noticed in your file that you are trying to map the double quote character: "
That might be difficult. At a minimum you need to escape that character with / or \ as double quotes are used as delimiters *in* the Resource file. Maybe tackle that key last, or nearly last when you have a bunch of other stuff working properly.
I want to hear how you are coming along with this. Be sure to post your results.
Good luck!
Brian.