Include picture

[YoseMite]

Hi,

Is it possible in AutoITscript to include a picture in a .exe file?

So that I not a extern picture have..

Thanks,

YoseMite

[Valuater]

yes..

FileInstall()

help has very good demo's at the bottom of each page

on your computer press the following

Start > All Programs > Autoit v3 > Autoit Help File

when that loads then press the "search" tab

then type in "?your search?" and press "List Topics"

**** you can do this with any word you want

thats what i do all the time

8)

[YoseMite]

Ok thanks.

But I want a picture in the *.exe so that I can load the GUI with the picture.

And that the picture doesn't load in a folder..

[Valuater]

ok... the fileinstall() will place the external picture inside the exe...

when you run the exe.. it will set the picture in a temp folder...

if you use this style ( this is what i use )

$Logo_jpg = @TempDir & "\XPClean-logo.jpg"
    FileInstall("C:\XPClean-web\Settings\XPClean-pics\XPClean-Main-Pic-Jpg.jpg", $Logo_jpg) ;source must be literal string

the temp file is hard to find and some one would have to look for it

C:\ >documents and settings > username > local settings(usually hidden) > temp

then... when the script is terminated.. you can delete the picture from the temp folder..

that way it is only exposed while your script is running

8)

[PartyPooper]

Thanks for that expanded explanation of how FileInstall works Valuater. Just say I'm not concerned about whether or not the user sees the pictures, would there be any benefit to using FileInstall? I'm thinking that using FileInstall will slow the execution of the script down because of it's increased size and I may be better off just including a 'picture' directory with the script. Would this be a truism?

Thanks

[SpookMeister]

Make it conditional. Have it check if the file exists first, then only if it isnt there install the picture. This would make the copy only happen the first time they run it.

Not to mention that the time involved for copying a reasonable sized image file will not be very long at all.

[Sokko]

Thanks for that expanded explanation of how FileInstall works Valuater. Just say I'm not concerned about whether or not the user sees the pictures, would there be any benefit to using FileInstall? I'm thinking that using FileInstall will slow the execution of the script down because of it's increased size and I may be better off just including a 'picture' directory with the script. Would this be a truism?

If you're not concerned about that, the sole benefit of FileInstall is convenience. It's easier to distribute a single file without anything else connected to it and know that, no matter what situation you put it in, it will run correctly, and it's not possible to accidentally delete or move any of its resources. The only slowdown that occurs is when the files are initially extracted from the executable. Plus, if you just leave them in the temp folder and don't delete them, this only needs to happen once.

Make it conditional. Have it check if the file exists first, then only if it isnt there install the picture. This would make the copy only happen the first time they run it.

FileInstall already does this by default. It will only extract the file if it doesn't already exist at the target location. Adding a third "1" parameter, on the other hand, will make it overwrite the file every time, as in FileInstall("source","destination",1). Useful during development when you are changing the contents of the installed file.

[PartyPooper]

Thanks Sokko.