who is setting path for templates and scripts

[ente]

Of course it is not vital, but I still would like to know why it it like this (and what I would have to do against it:

Even so I have wirtten in the directories settings dialogue

p:\abc\pocomail\templates
and
p:\abc\pocomail\scripts

...the scripts find the templates only when they are copied to

p:\abc\pocomail\mail

I also checked with the ini files for the scripts, but found no way to set a path there either.

Cordially
Götz Perll

[Michael]

I would suggest using the $scriptpath and $templatepath builtin variables for the paths. I have not had any problem finding the templates when I use these constructs.

[ente]

I would suggest using the $scriptpath and $templatepath builtin variables for the paths. I have not had any problem finding the templates when I use these constructs.

Thank you, Michael,

could you please tell where they are and where and how to place them
tnx

[Michael]

These are builtin variables that you would use in a script, something like:

Code: Select all

AddStrings $File $ScriptPath "myscript.poc"

[ente]

These are builtin variables that you would use in a script, something like:

Code: Select all

AddStrings $File $ScriptPath "myscript.poc"

Tnx, Michael,
sorry for being stubborn. Does that mean that I have to put in every script file the line you send me and there, instead of "myscript.poc", I have, when the name of this script is "ABEstrpl.poc", to replace your myscript.poc by this?

Shall I place this line at the beginning or at the end?

Have I somewhere in the script to mention the path?

Is this somewhere described in the pocoscript reference?

Why have I to write this in the script?

Why have I to set the script path in the Tools/Options/directories - what means, in the .ini-File is this path set and the program should know about? An old, a very old bug - then I'm wondering aout this for at least three, even four years?

[Michael]

The builtin variables are described in the "Variables" section of the Poco Script reference manual.

As to whether you have to put this in every script, I would think not, only those where you have the need to read files. I don't know what you are using scripts for so it is difficult to say how many. In my instance it would be very few scripts I would need to change.

Also, note that there is a builtin variable that gives you the name of the current script: $PocoScriptName