I did as you suggested, closed MC, installed the plug-in, and opened MC again. it opened with MC and warned me that it could not register Win-Ctl-p, as it might be registered with something else. I have no idea, but I hit okay, it warned me again, and I hit okay again, and then I went to plugin manager and "showed" the plugin, clicked on it in the tree, hit about, hit the register tab and it showed evaluation expired for the info.
I hit the enter registration button, navigated to the JDA file I saved from the email registration I got from Rhino, and it said thank for registring and to restart MC to validate, but when I close and re-open MC (I verified it shut down with Task Manager) it warns me again about the Win-Ctl-p and opens up immediately, but still shows evaluation expired everywhere and does not show as registered.
Are you perhaps running Windows Vista or Windows Seven?
By default, the plugin saves its config file in the Windows folder, which these OSs don't like.
If you go to your "Users\[your account]\AppData\Roaming\" directory and make a new folder there called "PlayingNow".
Then go to your Windows folder, find the file called "PlayingNow.ini" and copy it to the PlayingNow folder you just created. Now rename this new file to Settings.ini.
From now on, the plugin will read this file ("Users\[your account]\AppData\Roaming\PlayingNow\Settings.ini") instead of the file in the Windows folder.
Open this Settings.ini file in Notepad and look for the "Popup" section. You will find:
ShowHotkey=Win+P
ToggleHotkey=Win+Ctrl+P
Another application you use has already bagged the Win+Ctrl+p combo for itself which is why the plugin throws an error about it when it runs. When I press that combo on Windows Seven I get what looks like a display picker panel pop up. Change the combo in the Settings file and then save your changes. That should take care of the error message, which if nothing else, tells us that the plugin is running.
I tried this several times, as I was originally using a shared library, then I tried a library shared library, then a local library, all the steps above with each library, I tried installing your dll over the installed one a couple of times, and I can see it changes the plugin, because it shoes 9.0 instead of a greyed out button after replacing the dll.
I wonder why it won't install. do you have any ideas? Does Jim or Matt know why it won't register. It seems it's not supported any more, but I would love to get it working again if possible, it's a great little addition to MC.
Thanks again for all your help
I'm not sure what's up at your end, but everything went very smoothly for me here with a virgin MC installation. I did not need to go anywhere near the plugin manager. I installed the plugin, opened MC, and it ran. Simples. Then I closed MC, copied the new .dll into the plugin directory, over writing the existing file, restarted MC, and all is good.
"I can see it changes the plugin, because it shoes 9.0 instead of a greyed out button after replacing the dll."
This has me scratching my head a little as I can't imagine what you mean. The updated .dll file has a version number of 14.0.1, but that won't show up anywhere in MC as it installed v13.0.10 and that is what gets written into the registry location that the plugin manager reads its info from. MC is blissfully unaware you have swapped in a new file.
Where are you seeing "9" and which button is greyed out?
Your chosen library should have no bearing on the plugin's operation.
You should get 14 days grace before requiring to register. If your evaluation has expired, I guess you previously installed the plugin more than 14 days ago.
Your serial number is stored in the registry, which causes me to wonder if you are bumping into any possible registry writing permissions that might be in place on your system. I run with UAC turned off, do you?
If not, perhaps you could try turning it off, reboot afterwards to effect the switch off, apply the registration, does it work?, turn UAC back on, reboot to effect the switch on.
If that doesn't work, I have a plan B, but we can't discuss that here
-marko