Compile

[EliTe_ThuT]

Hey,

I wanted to know if there was a way to do like c++ and to include a image file inside a .exe (when compiling) so we can use it in that script without having to have the image in a directory or something...

Thx

[James]

I was just going to post that in the AutoIt Feature Requests, but I did a search.. And I found yours, but I think its been asked before.. I will edit in a minute.

[BrettF]

I was just going to post that in the AutoIt Feature Requests, but I did a search.. And I found yours, but I think its been asked before.. I will edit in a minute.

File Install to temp, file delete from temp

[James]

Lol, good point, but I think he means so you dont have to do that.

[BrettF]

Lol, good point, but I think he means so you dont have to do that.

Far as I know... there is no other way

[EliTe_ThuT]

Far as I know... there is no other way

But what is this install temp way??

[erebus]

FileInstall("blah.jpg", @TempDir & "\blah.jpg", 1) ; Install from script's dir to windows temp dir and overwrite if already exists
; The rest of your code here
FileDelete(@TempDir & "\blah.jpg") ; Delete the file before the script end
Exit

[EliTe_ThuT]

FileInstall("blah.jpg", @TempDir & "\blah.jpg", 1) ; Install from script's dir to windows temp dir and overwrite if already exists
; The rest of your code here
FileDelete(@TempDir & "\blah.jpg") ; Delete the file before the script end
Exit

But why would people use that...if they need the image...and if it's in the script dir...just call it from the script dir...why installing it to temp???

[erebus]

It's so simple. You use this trick if you don't want your users to see what the graphics of your script are.

In addition if you don't want even to alter them, you may use MD5 or other hashes to check either each file's integrity and so on.

If you don't see a reason to use such a thing, then don't. Use the classic way instead.

Edited May 6, 2007 by erebus