forum.vdsworld.com

[trapper]

In the multiple dialogs demo that ships with VDS it reads:

[Mac]

The last post here is a simple example of sending messages
to two windows:

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

Cheers, Mac

[trapper]

Thanks Mac. I'm assume the Timer event is not necessary but is just used in this instance to show how to send messages to either window and that the main thing to note is the EVLOOP and event handling. It doesn't seem difficult at all... or does the difficulty envisaged in the rem statements of the multi-dialog example apply when you have more than 2 dialogs and have to keep track of them?

Regards.

[Mac]

Actually the most inconvenient aspect of the whole thing
(in my opinion) is the fact that child window ID numbers
don't stay the same when ya close one - all numbers above
the one ya close decrement so there are no gaps in the
numeric sequence.

Other than that, it's pretty much straightforward.

Cheers, Mac

[Serge]

one little trick i use when i have several child windows is to create them all when the program runs and then hide the ones i don't want seen

and when a user clicks on a window to "open", i just unhide it

this way my numeric sequence stays the same and i know which child has which number

serge

[Mac]

Prolly not a bad idea Serge.

Ya can also store window names in a list - if ya add/delete
names as they are created/closed, the list index number
will always be the matching dialog number for that name.

Just remember to store the main window first, as its number
is always zero.

Cheers, Mac

[Serge]

excellent idea mac

serge

[jules]

What would be the best solution to this? Not having the ID change isn't really an option, because the dialogs really are stored in a list, so when you close one from lower down the list, the higher ones all move down one. And changing the behavior would break programs that rely on this.

Perhaps what's needed is a @DLGID() function that returns the current ID of a named child dialog?

[ShinobiSoft]

[Serge]

that might be a good idea jules

serge

[trapper]

Serge,

I've tried your idea of creating and hiding the child dialogs initially. It seems to work fine for the most part but I'm having trouble positioning the child windows where I want them to be.

I base the child window position on the main dialog. When it comes time to SHOW the child dialog I'm trying to position the window using the WINDOW POSITION command. However, I can't seem to do it while the window is hidden. Yet, if I unhide the window and then position it with the very next statement I see a visible jump of the window on screen.

Is there any way to position the child window while it is still hidden?

Regards.

[Serge]

hi trapper,

off hand i don't know as i never tried what you are trying to do - what about initally creating the dialogs where you want them prior to hiding them so when you unhide them then they will be where you want them?

serge

[Serge]

hi again,

i just tried with one of my programs and i can move the dialog while hidden so i'm not sure what happened at your end

i tried using vds 5 on windows 98se

the code i used was

[trapper]

Ok.. I'll try again with WINDOW HIDE and WINDOW NORMAL... I was using DIALOG HIDE and DIALOG SHOW.

It's not much use initially creating them where I want them to be as they are based on the position of the main dialog, which the user may reposition by dragging anytime they are using the program.

I've got to go to rush off to work so I'll have to wait till later though


Regards.

[jules]