by onenonymous » Sat Aug 01, 2009 10:31 am
nynaevelan wrote:One:
A question for you because I am having trouble with a few scripts due to the data RC4S adds to the vbs file. Why does the script add the (o) to the end of the sub section? I only ask because if the script has extra data in the sub name, the script will not run unless I change it . An example is the Export to iTunes script, the sub is sub ExportToItunes(Item) but it needs to be sub ExportToItunes for it to run along side RC4S. Is there changes I can make to RC4S for it not to add the (o) and will it break it if I do?
Nyn
The (o) indicates it needs to pass an object to the 2nd procedure and is needed in cases where the 2nd procedure needs the object. This was the missing piece way back when I was originally creating the script. The code that RCFS adds to the script won't interfere with the scripts normal functioning - ie if you run the other script off Tools/Scripts menu and it fails, then RCFS is not the cause of the failure.
In this case, I tried loading the Export to iTunes script and as scripted, it errors out when run off the Tools/Scripts menu. Change the line in the Export to iTunes script that you identified and it works fine off of Tools/Scripts. My guess is when he moved the script to the Auto folder AND made a Scripts.ini entry with Script Type 0 - that caused the problem. The Script Type 0 puts it into the Tools/Scripts menu, but if so, the main script then needs "sub ExportToItunes" as opposed to "sub ExportToItunes(Item)". If the scripter adds a menu item or button elsewhere to trigger the script - then it needs the "(item)" portion.
Are there other scripts you're having challenges with RCFS?
[quote="nynaevelan"]One:
A question for you because I am having trouble with a few scripts due to the data RC4S adds to the vbs file. Why does the script add the (o) to the end of the sub section? I only ask because if the script has extra data in the sub name, the script will not run unless I change it . An example is the Export to iTunes script, the sub is [color=#FF0000]sub ExportToItunes(Item)[/color] but it needs to be [color=#FF0000]sub ExportToItunes [/color]for it to run along side RC4S. Is there changes I can make to RC4S for it not to add the (o) and will it break it if I do?
Nyn[/quote]
The (o) indicates it needs to pass an object to the 2nd procedure and is needed in cases where the 2nd procedure needs the object. This was the missing piece way back when I was originally creating the script. The code that RCFS adds to the script won't interfere with the scripts normal functioning - ie if you run the other script off Tools/Scripts menu and it fails, then RCFS is not the cause of the failure.
In this case, I tried loading the Export to iTunes script and as scripted, it errors out when run off the Tools/Scripts menu. Change the line in the Export to iTunes script that you identified and it works fine off of Tools/Scripts. My guess is when he moved the script to the Auto folder AND made a Scripts.ini entry with Script Type 0 - that caused the problem. The Script Type 0 puts it into the Tools/Scripts menu, but if so, the main script then needs "sub ExportToItunes" as opposed to "sub ExportToItunes(Item)". If the scripter adds a menu item or button elsewhere to trigger the script - then it needs the "(item)" portion.
Are there other scripts you're having challenges with RCFS?
