Jump to content

Compiled Script


anixon
 Share

Recommended Posts

I have a script which when run processes without any errors however when the script is compiled I occasionaly get a message which tells me the line number at which the compiled version fails. Given that the script has some standard AutoIT #Includes as well as some that I have created for my own purpose the simple question is how do I identify the line number for the code in the #include which is cause the compiled version of the script to fail.

For example is it possible to process the script and the #includes into one file which can then be reviewed in the line order it would be in when compiled.

Assistance is always appreciated... Ant Posted Image

Link to comment
Share on other sites

  • Moderators

anixon,

Run the code through Obfuscator when compiling and it produces a file "filename_Obfuscated.au3" in the same folder as your script which is what the compiler actually uses to produce the final script. If you use the /StripOnly parameter with Obfuscator you automatically strip all the comment and blank lines and unused function code, so the line given in the error message would refer directly to that line in the Obfuscated file. Easy to find the error line number now! :)

If want to try this, you need the full SciTE4AutoIt3 package, which you can download from here. You get lots of other goodies as well, so it is well worth it if you have not already done so. ;)

Just add this to the top of your script:

#AutoIt3Wrapper_Run_Obfuscator=y
#Obfuscator_Parameters=/so

M23

Public_Domain.png.2d871819fcb9957cf44f4514551a2935.png Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind

Open spoiler to see my UDFs:

Spoiler

ArrayMultiColSort ---- Sort arrays on multiple columns
ChooseFileFolder ---- Single and multiple selections from specified path treeview listing
Date_Time_Convert -- Easily convert date/time formats, including the language used
ExtMsgBox --------- A highly customisable replacement for MsgBox
GUIExtender -------- Extend and retract multiple sections within a GUI
GUIFrame ---------- Subdivide GUIs into many adjustable frames
GUIListViewEx ------- Insert, delete, move, drag, sort, edit and colour ListView items
GUITreeViewEx ------ Check/clear parent and child checkboxes in a TreeView
Marquee ----------- Scrolling tickertape GUIs
NoFocusLines ------- Remove the dotted focus lines from buttons, sliders, radios and checkboxes
Notify ------------- Small notifications on the edge of the display
Scrollbars ----------Automatically sized scrollbars with a single command
StringSize ---------- Automatically size controls to fit text
Toast -------------- Small GUIs which pop out of the notification area

 

Link to comment
Share on other sites

anixon,

Run the code through Obfuscator when compiling and it produces a file "filename_Obfuscated.au3" in the same folder as your script which is what the compiler actually uses to produce the final script. If you use the /StripOnly parameter with Obfuscator you automatically strip all the comment and blank lines and unused function code, so the line given in the error message would refer directly to that line in the Obfuscated file. Easy to find the error line number now! Posted Image

If want to try this, you need the full SciTE4AutoIt3 package, which you can download from here. You get lots of other goodies as well, so it is well worth it if you have not already done so. Posted Image

Just add this to the top of your script:

#AutoIt3Wrapper_Run_Obfuscator=y
#Obfuscator_Parameters=/so

M23

Thanks M23 I have tried your solution and it works just fine. As always your assistance is much appreciated. Best Wishes Ant.. Posted Image
Link to comment
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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...