Not really a WinBatch problem BUT

[seckner]

Hoping you've seen this before... When in Studio, debugging a dialog script, and the dialog will minimize itself - doesn't matter if your typing, selecting, anything else, it simply minimizes... reopen it from the task bar and it will remain forever after. Any ideas?

[Deana]

Are you sure the dialog is actually minimizing or is it possibly just moving behind the Studio window. To confirm try using alt-Tab to tab through the various windows when you believe the dialog is minimized. If it is in the alt-tab list it is NOT minimized.

Keep in mind that when you debug in the WinBatch Studio environment, the studio window must stay active when stepping through the code. This allows you to see what line is currently executing.

[seckner]

Found, on my system anyhow (Win7 x64, dual monitors) that putting IntControl( 1002, 0, 0, 0, 0) at the top of the script fixes that. Thank you for your quick reply!!

[Deana]

Keep in mind that all running WIL scripts have a main window that is a 'box' running minimized as an icon on the Task bar. Any time you call a WIL dialog that dialog is created from this main box window/icon. For example, the BoxOpen box *is* the Winbatch main window. The dialog will always appear on top of it.

IntControl 1002 sets the display state of the WinBatch icon for the duration of the script. The default display state is minimized. The code you added tells WinBatch to hide its icon/window.  If any Box[..] functions are used to display information, the WinBatch icon will return to its previous display state.