Re-OPEN SOLVED: Addressing regular Qcad scripts
Posted: Wed Aug 28, 2019 3:35 pm
Andrew,
To make use of the addSpline simple API I included simple.js in my script.
Just as prescribed but I had to use 'include("scripts/simple.js");' ... and more
I had to put the physical scripts under the Qcad scripts folder.
Along with the script files: simple_create.js, simple_info.js, simple_input.js, simple_modify.js,
simple_transaction.js, simple_view.js.
And those are simply included by simple.js as a plain 'include("xyz,js").
Something similar is true for sprintf.js.
All in contradiction with eg. library.js that used to be not included in my script with no file present.
Or the inclusion of EAction in Misc.js as 'include("scripts/EAction.js");' with no file present.
I presumed that all scripts where present as compiled versions in a Win installer.
It seems that this is made straightforward for some but not for all.
OR
I am completely missing something here.
Regards
To make use of the addSpline simple API I included simple.js in my script.
Just as prescribed but I had to use 'include("scripts/simple.js");' ... and more
I had to put the physical scripts under the Qcad scripts folder.
Along with the script files: simple_create.js, simple_info.js, simple_input.js, simple_modify.js,
simple_transaction.js, simple_view.js.
And those are simply included by simple.js as a plain 'include("xyz,js").
Something similar is true for sprintf.js.
All in contradiction with eg. library.js that used to be not included in my script with no file present.
Or the inclusion of EAction in Misc.js as 'include("scripts/EAction.js");' with no file present.
I presumed that all scripts where present as compiled versions in a Win installer.
It seems that this is made straightforward for some but not for all.
OR
I am completely missing something here.
Regards