On 4/4/2012 4:34 AM, David wrote:
Will I have to code seperate DialogEventHandler functions for each of
the two dialogs?
You could have a single dialog proc that handles multiple dialogs, but
that can get unweildy pretty quick. The best practice is to have an
event handler for each dialog.
Also, if I have a button in my dialog1, that when pressed, will open
dialog2. As the things stands right now, it keeps dialog1 open in one
window, and then opens dialog2 in a second window. Any tip, how to get
the dialog1 disappear temporarily.
Set the parent of the second dialog to the first when you make your
dialog call.
Dialog myDialogXML, "dialog2", "Dialog2Proc", , dialog1.Window
Note the missing parameter. If you supply one, even with Nothing, you'll
have to handle it in your dialog proc.
Aaron
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
