en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en id en en en en nl en en en en en en en en en en en de en id de nl en en en en nl en en en en en en en en en en en en nl uk en en en en en de en en en fr en en en en en en en en en pt en en en en en en
By logging into your account, you agree to our Privacy Policy, personal data processing and storage practices as described therein.
Forgot password or user name?
Search in titles only Search in PowerBASIC for Windows only
You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
All Time Today Last Week Last Month
All Discussions only Photos only Videos only Links only Polls only Events only
Join Date: Apr 1999
15 Nov 2000, 11:04 AM
originally posted by lance edmonds in http://www.powerbasic.com/support/pb...ead.php?t=2889:
dialog end, like enddialog(), should *only* be used in the dialog box procedure for the target dialog. neither of your examples obey this rule.
see enddialog() in win32.hlp for more information.
dialog end is a wrapper for enddialog(), so the same basic rules apply to both the statement and the api call.
ok, so i looked in win32.hlp. according to that, enddialog() should only be used with modal dialogs.
but dialog end is used on both modal nad modeless dialogs. if it's just a wrapper for enddialog(), shouldn't we be terminating our modeless dialogs by some other technique?
and if dialog end is ok to use with modeless dialogs, does the "use dialog end only within callback" rule still apply?
[this message has been edited by dan soper (edited november 15, 2000).]
Join Date: Mar 1999
15 Nov 2000, 11:21 AM
As far as I've experienced, DIALOG END can be used from within any SUB or FUNCTION, not only
in explicitely connected CALLBACK FUNCTIONs. The only difference is that outside such a CALLBACK
FUNCTION you cannot use DDT-keywords, e.g. CBHNDL. Instead you must use the dialogs genuine handle.
This can be achieved by giving it global access.
GLOBAL hDlgGlobal AS LONG SUB BuildDialog DIALOG NEW ................... TO hDlg& hDlgGlobal = hDlg& ' here your code to build controls etc. SHOW DIALOG .... END SUB
Using hDlgGlobal you now can access the dialog from everywhere in your program.
Egbert Zijlema, journalist and programmer (zijlema at basicguru dot eu)
*** Opinions expressed here are not necessarily untrue ***
Copyright © 1998-2022 PowerBASIC Tools, LLC - All Rights Reserved.
Powered by vBulletin® Version 5.7.0
Copyright © 2022 vBulletin Solutions, Inc. All rights reserved.
All times are GMT-5. This page was generated at 01:48 AM.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.