>
> Alan,
>
> Your dialog.dll is very^10 nice!
Thanks
> I noticed that you didn't close the hDlg in your modeless example in
> "dialogPluginTest1.powerpro" dialog.version= 0037
Fixed that, I think, in 0.39 which I'm about to upload.
Rule is: you must provide exactly one control, typically button,
with <id> "cancel" and another with "ok". It's safe to destroy the
handle for the current dialog in the scripts attached to those controls.
There's also the dialog termination script, which is meant only to do
stuff like kill off events -- stuff exterior to the dialog. It's
_not_ safe to destroy a dialog in that script.
> Although the following works, you may be able to develop a better
> method... Eg, Save the handle during hDlg.Create or hDlg.Run and
> Pass the handle as you do for: sUserArg, hDlg, iCtrlNo, wMsg, lParam
> to the function the user defines in DIALOG.define.
I will pass handle to the termination script actually I think I did it
in the version I'm about to upload, but haven;t documented yet -- but
dire health warnings about trying to use it to destroy the dialog.
Attention: PowerPro's Web site has moved: http://www.ppro.org
SPONSORED LINKS
| Computer monitoring software | Power pro | Computer and internet software |
| Free computer monitoring software |
YAHOO! GROUPS LINKS
- Visit your group "power-pro" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
