Thanks for the input... unfortunately we got lost in the developer paper
chase and never gained access to the infamous OS sources, otherwise I would
have looked there first.
Right now I'm writing a MyDoDialog based on a typical app event loop. I hope
that I'm paddling in the right direction!
..Geoff
----- Original Message -----
From: William F. Weiher III <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 12, 1999 10:00 AM
Subject: RE: FrmDoDialog Questions
> The code is fairly simple, just copy it from the OS sources and modify it
> appropriately.
> To get out, just create a fake button event that you event handler does
not
> use an add it to the queue
>
> -----Original Message-----
> From: Geoff Shepherd [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 12, 1999 10:34
> To: [EMAIL PROTECTED]
> Subject: FrmDoDialog Questions
>
> I'm using FrmDoDialog in a couple places in my app to show modal forms. I
> have two problems that someone here might know the answer to..
>
> 1. The only way I know to exit FrmDoDialog is to let one of my buttons
pass
> through the dialog's event handler as not handled. This causes FrmDoDialog
> to close and exit the dialog. However, what if I want to exit the dialog
> programmatically from a non-button event? Is there an event I can queue
or
> an API routine I should call to cause this?
>
> 2. I'm a control freak! Seriously, my project is a vertical market app and
> takes control over the hard buttons and silk buttons. No problem in my own
> event loop, but how can I intercept hard button and silk button events in
> FrmDoDialog's event loop? I have a funny feeling I'm going to end up
writing
> my own FrmDoDialog... is it as easy as I would think it is (a glorified
> event handler)? Has anyone written their own FrmDoDialog and could pass a
> snippet of code along so I don't have to reinvent the wheel?
>
> Thanks in advance..
>
> --
> Geoff Shepherd
> mailto:[EMAIL PROTECTED]
>
>
>
>
>
>
