| Nelson Kaye 2006-09-02, 6:55 pm |
| Robert,
I tried your suggestion, and found, as you stated, that WM.TakeCloseEvent()
does trap the X. I also found that if I made a change to the record, it
causes a popup right before returning - asking if one wants to save changes
to the record.
I am still not clear on what is the proper windows action to be taken on
pressing X:
Should pressing X on the title bar be the same as pressing the OK
(accept) button on the form?
If so, should the popup asking if ones wants to save changes be somehow
bypassed? Or is this the proper (standard) procedure? In some cases, when
I trap OK to go to embed code, I actually perform the record update there,
in which case the X pop-up message is academic - unless I can distinguish in
WM.TakeCloseEvent() whether it came from OK or X - and of X, cause (or
create) a popup at that point, and close the update if the user says
'Cancel'. However, if I do my own pop-up, and the user continues, then I
would get the system X popup afterwards.
"Robert Peros" <no_spam.robert.peros@zg.t-com.hr> wrote in message
news:A921.1157207982.11474@discuss.softvelocity.com...
> "Nelson Kaye" <nkaye1@nyc.rr.com> wrote in message
or[color=darkred]
> WM.TakeCloseEvent() cover both event.
> WM.Completed() only Completed->OK
>
> R.
>
>
>
>
>
|