Re: Who can write an inputbox.e?
Pete,
Hmm,
Well, I'm thinking that the problem isn't exactly that a dialog (for an
inputBox) would have to create the inputbox as a child of a specific window,
but rather that Liu's inputbox was the *main* window, which would seem to be
undesirable. The "messageBox" function somehow gets around having to make
it an (explicit?) child of some window, but that's apparently by a wrap of a
call to a .dll.
Could easily be I'm way off base here & am missing something obvious.
Dan Moyer
----- Original Message -----
From: "Pete Lomax" <petelomax at blueyonder.co.uk>
To: "EUforum" <EUforum at topica.com>
Sent: Wednesday, January 22, 2003 3:54 PM
Subject: Re: Who can write an inputbox.e?
On Wed, 22 Jan 2003 03:18:47 -0800, Dan Moyer
<DANIELMOYER at prodigy.net> wrote:
>makes the inputbox the *main* window, whereas the intention would be to be
>able to use the function to put an inputbox in (& child of) another window,
>right?
>
>This was one of the difficulties I had when I tried to do make an inputbox
>include, namely that the included code should preferably be able to be
>placed near the beginning of a program, so it could be used whenever
>desired, but because it would have to be able to make the inputbox window
be
>a child of another window, it would have to be placed *after* that window
>was created (and after *any* window that might want to use it).
Hmm... I mentioned this before as I was not sure, but got no answer...
>Somehow messagebox avoids that requirment!?!
Can you explicitly state the problems with a dialogue not being the
child of a specific window?
Pete
==^^===============================================================
This email was sent to: DANIELMOYER at prodigy.net
TOPICA - Start your own email discussion group. FREE!
|
Not Categorized, Please Help
|
|
