11 posts in this topic
I'm using UseTraySetIcon("shell32.dll", xx) to set my tray icon to a specific icon while running, is there a way I can specify this icon when I compile my script into an exe so my exe icon is the same?
If I embedd a compiled autoit script into my new script, is there a possibility to pass some data from the compiled embedded exe to my script?
I know it's possible with an ini or txt-file. But is there something without creating a file? I plan to return an array or an unformatted string of datas with delimiters inside.
I am having issues with Windows SmartScreen blocking my compiled scripts. They run fine on my computer, but when I move them over to a different one, either by USB or a file hosting site, they get blocked by Windows SmartScreen. I have tested it on a number of computers, and it happens on all of them. I have also done this with scripts that do and don't require Admin, and it always happens.
Is that related to this? I was thinking it might be, but I am not so sure since the only antivirus I have is Windows Defender. I wouldn't mind this happening since I realize you can click More info and then click run anyway, but I am planning on distributing my program, and normal users probably wouldn't know this. I don't really want to have to deal with all the users complaining that my program has viruses.
would there a way to disable enable the CUI after the exe was compiled If a certain Action is being used?
please bare with me for a moment here...
My goal: To be able to take the error line number returned by the EXE file and locate the actual line in the source.
I believe most of the AutoIt users are coming to this issue at some point.
I realize the final source, before the compilation is done, is the combined source of all the include files and the main script etc. So I figured if I have a way to get this combined source, that would give me a solution to this problem. And I spent the last couple of days (more than 10 hours a day) searching in the forum and asking some questions in different threads. And with the help of few people, I found a way (using the Obfuscator) to get this source and the line numbers were actually MATCHING!
However this solution introduced a WHOLE LOT of other problems for me and broke some of the functionality in my script since it has a lot of Call() and ObjEvent() functions. My code turned out to be un-obfuscatable. And for the record, I do not need any obfuscation done at all, nor I need the unused included functions stripped down (even though it made my EXE a 30% smaller). I needed the Obfuscator just to get this final piece of code to be able to achieve My goal.
So all this got me thinking... Please correct me if I'm wrong, because I don not have any knowledge of the internals of a compiler.
Since Aut2exe is the one that combines all the code together and then working it's magic to create the EXE, there should be a pint in this process where that code is available in its final form. Then why isn't there a command line option to dump the final combined source in a file just before it is compiled?
Once again, I do not know the internals of the compiler but my logic dictates that this would be the most reasonable and straightforward solution.
Please share your thoughts and also, if any of you knows a way to achieve my goal without using the Obfuscator, I would LOVE to here it!
EDIT: And here is the solution: ( I've tried to explain it as simply as I can, so even the beginners can understand it.)