FScript 1.19 Issues

[Perry Mowbray]

I've been updating my plugins to the latest version of FScript (as requested in this thread).

First plugin went fine after I figured out what was going on.

So I headed onto #2 and it hasn't gone as smoothly as I'd hoped 

Plugin #2 uses vbScript, and worked fine in the previous versions of FScript that I was using. But after upgrading to 1.19 I think that FScript is not calling the onProcessTrigger function.

So I decided to start at the beginning, and I've converted the original javaScript examples to vbScript. I've attached them, if anybody else wants to check.

Note: I've left the signature for onProcessTrigger as was supplied with the original sample, but I've tried the other signature that works with my javaScript plugin without success.

[Perry Mowbray]

ecaradec has just got back to me about this onProcessTrigger issue.

He suggested that onProcessTriggerV2 be tried: and it works!

OK: Problem not solved but easily worked around. I have not tested the other languages, so I'm not sure if they affected in the same way; but if you are using something apart from javaScript and onProcessTrigger is not being called - Try onProcessTriggerV2

Thanks ecaradec 

[ecaradec]

Hello Perry,

I found the source of your problem, the issue is that the vbscript needs to declare every parameter used. You have to use the full function declaration even if you don't use every parameter. I probably added a parameter in the last version of fscript causing the vbscript call to fail now.  The full signature is :

function onProcessTrigger(path, caption, groupname, pluginid,thispluginid,score,entrytype,voidp)

The issue was very easy as the script engine returned an error code with exactly the correct issue. I really need to add some error messages  

[mouser]

now we have the real solution to all of the compatibility problems -- it is that all plugins need to upgrade to onProcessTriggerV2.

[ecaradec]

no, onProcessTrigger works, the issue is the number of parameters. Fscript pass all parameters to the scripting host. That's not a problem with javascript that is very forgivable about the number of parameters given. VBScript, ruby, etc... expect the exact correct number of parameters.
With recent FARR defining function onProcessTrigger(path, caption, groupname, pluginid,thispluginid,score,entrytype,voidp) will work all the time. Depending of the features of the language we could get full compatibility by defining a function that allow for extra parameters, or overload the function with one of the same name with a different set of parameters.

[cranioscopical]

I'm beginning to understand what the  'f' in fscript really stands for  

Thanks to everyone who's working on this in order to re-align the stars.

[Perry Mowbray]

I'm beginning to understand what the  'f' in fscript really stands for 

-cranioscopical (September 20, 2009, 06:46 AM)

I thought you already knew it was fantastic? 

[cranioscopical]

I'm beginning to understand what the  'f' in fscript really stands for 

-cranioscopical (September 20, 2009, 06:46 AM)

I thought you already knew it was fantastic? 

-Perry Mowbray (September 20, 2009, 09:27 PM)

Hoist by my own petard!

[ecaradec]

It's really F...Script. Guess what fits in ?

[Perry Mowbray]

It's really F...Script. Guess what fits in ?

-ecaradec (September 21, 2009, 01:53 AM)

I can think of a few things:


or

[cranioscopical]

It's really F...Script. Guess what fits in ?

-ecardec

I assume it's neither U nor me.
Perhaps it's FlimScript.
Watch for its companion, FlamScript 

Whatever it is, it certainly enables a lot of stuff, which I appreciate very much!