GUI def as include ?

[Myicq]

What strategies are best for complicated GUI definitions, if any, to make all more readable.

I tried yesterday to do something like

#include "complicated_gui_setup.au3"

 

to avoid having 200 extra lines in my script.

But now I could not compile my script because of warnings "used before declaration".  I can possibly use -w 3 parameter, but doesn't that disable syntax check completely ?

I guess what I try to achieve is something like @import url("file.css") where the file is inserted at compile time.

 

[l3ill]

 

What strategies are best for complicated GUI definitions, if any, to make all more readable.

 Use Region/EndRegion to tidy up your large scripts

The way I understand it, Includes are typically only for Functions and not for GUI's.

[Melba23]

Myicq,

Firstly, you can #include files at any point within the script - all AutoIt does is to add the code at that point. Most includes are designed to be at the start of the script, but yours sounds like an obvious exception.

However, I would not recommend doing this as you would have 2 scripts to maintain - change a variable name in one and the other will cease to function. If you use the #Region...#Endregion directives that are available with the full SciTE4AutoIt3 package then you can fold your 200 lines of code into a single one within SciTE - which gives you the same visual result but not the inter-file dependency.

M23