forum.vdsworld.com

Jimjams · Newbie Joined: 23 Sep 2002 Posts: 21

Here's the thing.
I wrote several programs which I'd like to combine into one big exe and then call the separate exes using command line parameters. This means that the combined exe has multiple dialogs.
2 of those dialogs use 'dialog set,<control name>'.
The first one is a task icon for which I use the 'dialog set,<control name>' to change the infotext whenever the status of the exe changes.
The other one is a "flash"-dialog with a progressbar. The other dialogs may or may not appear before or after these two dialogs and here's the problem; In order to set the next step for the progressbar or the infotext for the taskicon I need to know the dialognumber of the these dialogs so I can select them. Unfortunately they can change whithout an actual event occurring so I can't use the @Event(D)-function.

Is there a solution for this or am I just waisting my time? Sad

Skit3000 · Posted: Sat Oct 26, 2002 5:38 pm Post subject:

Maybe you can make something with the use of @winontop()...

Mac · Posted: Sat Oct 26, 2002 11:44 pm Post subject:

If I understand the question correctly....

You can use a list as an index for multiple windows.
Add the child window names to the list (add a blank
line to the list first, or the name of the main dialog).

When a child window is opened, add it's window title
to the list. When a child window is closed, use @match()
to find it's title in the list and remove it. The @index()
number will always be the dialog number for that window.

If several are open, use @winactive() to find the active
window, then @match() to search the list and retrieve
the @index() number (which is the dialog number).

Here's an example using multiple windows:

http://www.vdsworld.com/forum/viewtopic.php?t=714

Cheers, Mac Smile

Garrett · Posted: Sun Oct 27, 2002 2:26 am Post subject:

I find that using CLASS names for each dialog is much better, especially if
you change the title bar of the child windows. And you can use
@name(@datetime())@ext(@datetime()) to generate unique class names for
each child, or use one of the random number dlls or routines.

-Garrett

Mac · Posted: Sun Oct 27, 2002 6:14 am Post subject:

Or use your initials and a large incremented number.
Chances of duplicates by others on a given system at
a given time are kinda slim...

Using @datetime() is a nice idea Garrett. Wink

Cheers, Mac Smile

Garrett · Posted: Sun Oct 27, 2002 7:48 pm Post subject:

I did neglect to mention that I usually put the name of the program before
the datetime string to insure that it's even more unique, just like you
suggest using initials.

For me though, I've never had undetermined child windows... Mine have all
been planned out and giving them all unique names is rather easy since
they are all planned. But even if you have a program that allows
undetermined child windows, you should have no problems with giving
unique class names to each.

-Garrett

Jimjams · Newbie Joined: 23 Sep 2002 Posts: 21

Thanks guys!

Once again you're lifesavers... Razz

moke · Contributor Joined: 02 Jan 2002 Posts: 162

Dr. Dread · Posted: Mon Oct 28, 2002 7:41 pm Post subject:

Way to go, moke! VDS family planning.

Greetz
Dread

Garrett · Posted: Mon Oct 28, 2002 9:34 pm Post subject:

Ah man! Did I get to be the whipping boy on that one or what!! Wink

LOL!!!

-Garrett

Mac · Posted: Mon Oct 28, 2002 9:44 pm Post subject:

Lol Garrett, it's nice to know you believe in "planned
programming"... Very Happy

Cheers, Mac Smile

moke · Contributor Joined: 02 Jan 2002 Posts: 162

Sorry Garrett,
I couldn't resist. Smile

moke

Garrett · Posted: Tue Oct 29, 2002 5:40 am Post subject:

Ok, since we're on this.....

Do Trojan's keep our programs from producing little child windows???

-Garrett

SnarlingSheep · Posted: Tue Oct 29, 2002 5:51 am Post subject:

LoL, had to think about that one twice Wink

Ribbed for Microsoft's pleasure.

moke · Contributor Joined: 02 Jan 2002 Posts: 162

Good one Garrett,

I hate to sound old fashioned but what's wrong with abstinence until both
the programmer and the program are ready for commitment?

Too many programmers believe that just because they have a BIG
HARD DISC that they should use it, without thought for the
consequences. Well I say a little responsibility and moral fortitude go a
long way.

However, if you just can't resist all those opportunities for fun I have two
words for you:

VIRUS PROTECTION !!!

Laughing

moke

PS - Tommy, if this post crosses the line of acceptable usage my
apologies and feel free to edit or delete it. Just having a little fun Smile

.