Sign in to follow this  
Followers 0
piccaso

@scriptdir

4 posts in this topic

if the @ScriptDir macro is called from a included file.

witch directory does it return?

the callers or the called?


CoProc Multi Process Helper libraryTrashBin.nfshost.com store your AutoIt related files here!AutoIt User Map

Share this post


Link to post
Share on other sites



it'll be the directory from where the first script was...i guess u would call it the "caller"


-Brett

Share this post


Link to post
Share on other sites

Thx :)

I wanted to use @scriptdir to 'FileInstall' a binary from my lib. dir, but fileinstall doesent work with Variables anyway :huh2::D


CoProc Multi Process Helper libraryTrashBin.nfshost.com store your AutoIt related files here!AutoIt User Map

Share this post


Link to post
Share on other sites

FileInstall() should never need to use a variable for the source. The whole idea behind it is that you will be compiling the source eventually, and it needs to know the raw location of the file. Once it is compiled into a windows executable file it will put the file in the destination dir without requiring it to be on the user's computer. Simply put, the source becomes the script itself when you compile it.


[font="Optima"]"Standing in the rain, twisted and insane, we are holding onto nothing.Feeling every breath, holding no regrets, we're still looking out for something."[/font]Note: my projects are off-line until I can spend more time to make them compatable with syntax changes.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0