forum.vdsworld.com

[DW]

Just some general questions.

1. Whats is the best method of handling child dialogs? At the moment i create a dialog and then hide it before creating the child.
Is this a good or bad way of handling them? Should I use a way like the one in the example files that come with VDS?

2. Functions and commands, whats the difference? and how do I make functions/commands that return one or more values to another section of the script. Global variables. Also can you make function variables only that dont leak in to the script?

3. if and end functions, if i run an if condition which then goes to another labels mid function, whats the best way to make sure the if it is ended.

4. Lists, whats the best way to manage hidden lists and how do you make sure a list is closed eeven when caused to goto another label mid function?

5. include files, whats the best way to use this feature? Right now i have been using them to split the script up into sections. Is their more power in them?

6. resources, whats the best way to include the icos, bmps, etc into the exe? I find that when i use the resource command i cant run the script unless its compiled because the resources are not found.

7. Edit eliments, how can i make it so that only x number of chars can be entered? Also is their a way to limit the input, to say no symbols, etc?

Can anyone help me work this all out?
Thank you.

[Skit3000]

Here are the ones I knew from the head...

1. You can first create the main dialog, without the "DIALOG SHOW" command, and then create the child windows. This way, you can close the windows without closing your program itself.
   
   
2. The different between functions and commands is that commands don't return a value, functions do. A function can be spotted by the @functionname()-syntax. All other things like "list" and "dialog" are commands. If you want to use global variables within functions, just use variables which have two %-characters. All single-% variables can only be used in the function itself.
   
   
3. -
   
   
4. Just put a "list close,<number>" before the actual GOTO command.
   
   
5. If I have a large script with multipy dialogs, I put every dialog (with all its labels) into a new dsc file. I also put functions and commands in another file, so that I can easily find the code I want.
   
   
6. -
   
   
7. -
   
   

[DW]

with regards to number 1

[jules]

Just execute the DIALOG SHOW.

[Hooligan]

I deal with #3 like this: