Closing a Dialog Box

Hi everyone,

I have a problem concerning about closing Dialog Boxes. I have a script who is opening a module and closing and perfectly performing all actions during its execution for an opened module, however when it continues with the next module, i receive error messages, because i need to close the dialog box when i close the module. Nevertheless as i realize all actions in a void function, any close attempt in a void action is not allowed as i would be trying to access a global variable whereas i am in a local function, i mean in a void function. So my question, how can i close this box in a void function? Is there a way to do it?

Thanks in advance to everyone who pays attention.

Kind regards,

Melih
SystemAdmin - Wed Apr 15 06:10:07 EDT 2009

Re: Closing a Dialog Box
SystemAdmin - Wed Apr 15 06:16:54 EDT 2009

Re: Closing a Dialog Box
dpechacek - Wed Apr 15 08:20:48 EDT 2009

Re: Closing a Dialog Box
SystemAdmin - Wed Apr 15 08:57:31 EDT 2009

Re: Closing a Dialog Box
dpechacek - Wed Apr 15 10:45:13 EDT 2009

Re: Closing a Dialog Box
SystemAdmin - Fri Apr 17 04:26:21 EDT 2009

Re: Closing a Dialog Box
dpechacek - Fri Apr 17 08:30:31 EDT 2009

Re: Closing a Dialog Box
llandale - Fri Apr 17 09:11:27 EDT 2009

So if I understand: you have a main dialog that loops through all modules in a folder. For each module you open it, and sometimes offer the user a new dialog box to do some chore. When the user closes the module you want to close the dialog and continue with the main dialog action, proceeding to the next module.

Gads, good luck.

First off: for all but the simplest of dialogs, I found out very early on that your Dialog Box variables (DB and DBEs) must be global variables defined at the top of the script, since callback/apply/button functions routinely need to access them. The DB parameter just about must be defined globally. (OK, lets forget about defining some Skip list as parameter and storing local DB and DBE values in it; as that's practically the same thing). In your case, I cannot imagine a script that doesn't have these defined globally. All my scripts now define them all globally, I don't bother thinking about whether or not this particular script can get away with them locally.

In your case, when its time to close the sub-dialog, that's easy since the DB is a global variable.

Now, as for you starting-stopping-waiting for the user to do something; as I said, good luck. The main loop cannot be a routine recursive "for itm in fld do" loop. The main script will need to find out all the modules it wants to deal with, store these in some global structure (like a Skip), and keep track of which one it has finished working. Store them in a global Skip with data string 'NameItemFull' and key int 'Sequencer' which starts at zero and increments each time you insert a new item name. You'll need some function that gets the 'next' item; it loops through the Skip looking for item #n+1. When it finds it it increments global int n; then passes the string off to the function that opens the module and figures out if the sub-dialogs are appropriate. Some function will need to figure out if its time for the 'next' item, no doubt in the sub-dialog close function. You thus have a circular reference and will need to pre-define the function that finds the next item (near the top of the script). A pre-defined function looks like this:

string GetNextItem()
      // notice there are no braces {} for this pre-defined function
... other functions go here ...
string GetNextItem()
{ body of this function.  Notice the braces {} mean this is the actual function
}

Sounds like you'll need a special main-dialog close function that figures out if the sub-dialog is open, and offers to close it along with the module that's currently open.

Yacks, good luck.

>Louie

Re: Closing a Dialog Box
SystemAdmin - Wed Apr 22 08:09:45 EDT 2009