Re: engineering a global type a variable...
- From: David Wilkinson <no-reply@xxxxxxxxxxxx>
- Date: Tue, 09 Sep 2008 09:56:27 -0400
RAB wrote:
I am sorry, as I didn't make that clear. (dialog B) and (dialog C)
are not open at the same time. I want the user to click check boxes
on the administrator dialog (dialog B) and then close the dialog.
Depending on the users choice, this will affect a variable on (dialog
C). Specifically, (dialog C) has a timer that I want to change based
on the users choice on the administrative (diaolog B).
RAB:
Well, you want to store the values in these Dialog B check boxes in BOOL member variables of Dialog B, retrieve them after B closes, and pass them to C.
It is never necessary to use global variables to do this kind of thing.
This is not really an MFC issue; it is an object communication issue.
--
David Wilkinson
Visual C++ MVP
.
- Follow-Ups:
- References:
- engineering a global type a variable...
- From: RAB
- Re: engineering a global type a variable...
- From: Tom Serface
- Re: engineering a global type a variable...
- From: RAB
- engineering a global type a variable...
- Prev by Date: Re: How does PeekMessage really work?
- Next by Date: Re: CallNextHookEx/AfxCbtFilterHook => stack overflow
- Previous by thread: Re: engineering a global type a variable...
- Next by thread: Re: engineering a global type a variable...
- Index(es):
Relevant Pages
|