The Music Manager for Serious Collectors
http://www.mediamonkey.com/forum/
I am sorry, but your description in that report was not very clear to me. Beside of that, you are mentioning only change of PlayCount, but forgot to mention LastPlayed. And why you put that issue in Last.fm plugin Project when it could have some side effect with any script?Peke wrote:re 1. tracked and tested within http://www.ventismedia.com/mantis/view.php?id=7084
I have found a reason for that and reported in Mantis: Second Web Browser control on form has serious problem with Common.Anchors property [4.x]ZvezdanD wrote:5. some Web Browser controls are not displayed at all (Magic Nodes and RegExp scripts are affected); I am trying to find some solution, but I am afraid that this could be resolved only in the program itself.
Hi,jiri wrote:I added a small Wiki section that describes changes that might be needed for some scripts, it's here:
Making scripts ready for per-user installations
Starting from MediaMonkey 4.0, scripts can be (and are suggested to be) installed per-user, and so they don't have to be installed in Program Files folder, but are installed in local Windows folders. The mechanism in MM is internally make as transparent as possible, so that scripts don't have to care much about their installed location. That said, some pre-4.0 scripts might need tweaking. For example, a popular script Lyricator has >1000 lines, but there's only one change needed in order to get it working under local installation, namely:
Dim sAppPath: sAppPath = sdb.ApplicationPath & "Scripts\Lyricator\"needs to be changed to
Dim sAppPath: sAppPath = sdb.ScriptsPath & "Lyricator\"
Code: Select all
[Header]
ID=PlayedDateAndCounter
Title=Played Date & Counter
Description=Sets Played Date and Counter on playback startup
VersionMajor=1
VersionMinor=0
Type=Script
[Copy]
Src=PlayedDateAndCounter.vbs
Tgt={app}\Scripts\Auto\PlayedDateAndCounter.vbs
[Execute]
File={app}\Scripts\Auto\PlayedDateAndCounter.vbs
Function=OnStartupEyal wrote:Hi,jiri wrote:I added a small Wiki section that describes changes that might be needed for some scripts, it's here:
Making scripts ready for per-user installations
Starting from MediaMonkey 4.0, scripts can be (and are suggested to be) installed per-user, and so they don't have to be installed in Program Files folder, but are installed in local Windows folders. The mechanism in MM is internally make as transparent as possible, so that scripts don't have to care much about their installed location. That said, some pre-4.0 scripts might need tweaking. For example, a popular script Lyricator has >1000 lines, but there's only one change needed in order to get it working under local installation, namely:
Dim sAppPath: sAppPath = sdb.ApplicationPath & "Scripts\Lyricator\"needs to be changed to
Dim sAppPath: sAppPath = sdb.ScriptsPath & "Lyricator\"
I finally found why I had hard time debugging my new script under MM4!
- I'm running Windows XP, MM 3.2.4.
- I upgrade MM3 by installing MM4 in same folder. The folder already contained scripts in \Program Files\Mediamonkey\Scripts\Auto,
with my new script in it. So far so good. The scripts is working.
- I made some changes to my script, rebuilt the mmip and install it. The script now seems to run twice (?)
Reason: New mmip installation put the script in C:\Documents and Settings\Eyal\Application Data\MediaMonkey\Scripts\Auto, instead of overwriting the old one. So after restarting MM, 2 versions of the script are running simultaneously.
Here's the mmip:I think {app}\ should install in application folder. {usr}\ or another variable name might be used to install local folder.Code: Select all
[Header] ID=PlayedDateAndCounter Title=Played Date & Counter Description=Sets Played Date and Counter on playback startup VersionMajor=1 VersionMinor=0 Type=Script [Copy] Src=PlayedDateAndCounter.vbs Tgt={app}\Scripts\Auto\PlayedDateAndCounter.vbs [Execute] File={app}\Scripts\Auto\PlayedDateAndCounter.vbs Function=OnStartup
Is that what you meant by "The mechanism in MM is internally make as transparent as possible, so that scripts don't have to care much about their installed location." ?
Thanks
Eyal :~)
I don't think so. If you introduce something like that, none existing installer package would be compatible with MM4. During installation of the new version of script/skin, the program itself should uninstall the old version of the same script/skin, not matter if it is previously installed in local or global folder and not matter of the current user choice of the installation folder.Eyal wrote:I think {app}\ should install in application folder. {usr}\ or another variable name might be used to install into local folder.
Thanks, fixed as http://www.ventismedia.com/mantis/view.php?id=7273Eyal wrote: - I'm running Windows XP, MM 3.2.4.
- I upgrade MM3 by installing MM4 in same folder. The folder already contained scripts in \Program Files\Mediamonkey\Scripts\Auto,
with my new script in it. So far so good. The script is working.
- I made some changes to my script, rebuilt the mmip and install it. The script now seems to run twice (?)