Re: 2 parm vs. 1parm GetDlgItem() trouble . . .
This is a multi-part message in MIME format.
------=_NextPart_000_0058_01C9B755.51FA2160
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=response
Content-Transfer-Encoding: 7bit
Thank you. I think I almost understand. Rough being a newbie :)
As used -- GetSafeHwnd(); results in Unhandled exception at 0x5c5278dc
(mfc90ud.dll) in tst04.exe:
for:
gMBs.CtlBtn.m_Btn->SetBitmap( gMBs.CtlBtn.m_Btmp );
gMBs.CtlBtn.m_Btn is set from:
reinterpret_cast<CButton *>(GetDlgItem(DlgH,gMBs.CtlBtn.Btn_ID));
within the mpc.cpp attached.
Clearly -- I am missing some large overall consideration rule or construct.
I am working on an application for a stroke patient (my mother). I am
learning C++ and VS and MFC -- I've been a 'C' since the dino days.
This app defines 6 (six) jumbo size touch buttons (for now mouse click
buttons), these jumbo buttons will have a graphic bitmap (this is working)
\via this test code:
BOOL C_tst_04_Dlg::OnInitDialog()
{ . . .
static CBitmap m_bitmap;
CButton *m_Btn_1;
m_Btn_1 = reinterpret_cast<CButton *>(GetDlgItem(IDC_BUTTON1));
m_bitmap.LoadBitmap(IDB_BITMAP_Btn_1);
m_Btn_1->SetBitmap(m_bitmap);
.. . . }
Because of false/error hits/taps the design is to require two discrete taps
with the
first tape inverting the bitmap on the button -- so it becomes tagged -- the
patient gets visual feedback of what they are trying to do.
So I created a button click / bitmap inverting class. -- there is a 7th
button that
will although "paging" to additional sets of six jumbo buttons. But the
logic will
be the same for each page -- takes two discrete touches/clicks with
unlimmited
time inbetween -- to trigger the buttons action. The default icon will
show --
when the first click is made this icon is inverted. Check the attached
mpc.h and mpc.cpp (mpc is short for project MomPC).
BOOL C_tst_04_Dlg::OnInitDialog()
{ . . .
HWND DlgH = GetSafeHwnd();
gMBs.do_mpc_btn_init( DlgH ); // do the MPC button
initialization, bitmaps, counts, states, etc.
.. . . }
The tasks being done but these jumbo buttons is quite varied -- it seemed
to be in good coding practices to isolate the button and screen of buttons
logic and processing, no? But what worked fine inside of
C_tst_04_Dlg::OnInitDialog() is not working within gMBs.do_mpc_btn_init( )?
Do I explain this well enough?
Thanks again.
Sincerely,
Kevin Waite
"Giovanni Dicanio" <giovanniDOTdicanio@REMOVEMEgmail.com> wrote in message
news:e6tdbk1tJHA.5664@TK2MSFTNGP03.phx.gbl...
"Kevin Waite" <kevin001.waite@gmail.com> ha scritto nel messaggio
news:D01FE180-0B2B-47F0-B614-FE4003566E58@microsoft.com...
Newbie here -- in my default wizard MFC Dlg.cpp -- I can use GetDlgItem
with a single parm, say the ID of a button -- and it works great -- in
fact both decls are present -- the single parm
ID and the ( HWND hdle, ID ) ......
When I make a new class module -- xxx.cpp --- and include exactly the
same includes from Dlg.cpp -- exactly the same!
I don't get the single parm GetDlgItem( ID ) -- booo -- I only get the 2
parm (HWND, ID) ver . . . . rats rats rats
I think that with "single param ID" GetDlgItem() you mean the member
function of CWnd class:
http://msdn.microsoft.com/en-us/library/77d16yhw.aspx
CWnd* CWnd::GetDlgItem(
int nID
) const;
and with "the 2 parm (HWND, ID) ver" you mean the global Win32 API
function ::GetDlgItem:
http://msdn.microsoft.com/en-us/library/ms645481.aspx
HWND GetDlgItem(
HWND hDlg,
int nIDDlgItem
);
The first parameter 'HWND' in the member function version (the "single
param version") is implicit, because the HWND used is the one associated
to the particular instance of CWnd (your CDialog-derived class).
Instead, in the global function you must specify the handle of the
dialog-box you want to apply GetDlgItem to.
So -- either solution would be great --
a) how to get the single parm version of GetDlgItem vialbe from xxx.cpp
In general, in an MFC app, it would make sense to call GetDlgItem member
function within the CDialog-derived class. Why do you need the global
::GetDlgItem function?
Could you please post some code?
b) or how to querry the Dialog Handle in the form of HWND
In MFC, if you want to get the HWND associated to some CWnd (or derived)
class, you can use CWnd::GetSafeHwnd() method.
But I'm not sure if your design is good. If you post some code, I think we
could give better advice.
Note also that in MFC apps it would make more sense to add member
variables to CDialog-derived classes associated to controls (e.g. CListBox
m_myListBox), instead of calling GetDlgItem() method and cast the returned
CWnd pointer to some control class (e.g. CListBox * pListBox = (CListBox
*)GetDlgItem(IDC_MYLISTBOX)).
HTH,
Giovanni
------=_NextPart_000_0058_01C9B755.51FA2160
Content-Type: text/plain;
format=flowed;
name="mpc.cpp";
reply-type=response
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="mpc.cpp"
// mpc.cpp : implementation file
//
#include "stdafx.h"
#include "afxwin.h"
#include "_tst_04_.h"
#include "_tst_04_Dlg.h"
#include "DlgProxy.h"
#include "mpc.h"
#ifdef _DEBUG
#define new DEBUG_NEW
#endif
Mpc gMBs; // create our MomPC (Mpc) buttons class
void Mpc::do_mpc_btn_init( HWND DlgH )
{ /* do_mpc_btn_init() */
int i;
gMBs.CtlBtn.clks = 0;
gMBs.CtlBtn.stat = MPC_BTN_DIM;
gMBs.CtlBtn.Btmp_ID = IDB_BITMAP_Btn_7;
gMBs.CtlBtn.Btmp_ID_i = IDB_BITMAP_Btn_7i;
gMBs.CtlBtn.Btn_ID = IDC_BUTTON7;
gMBs.CtlBtn.m_Btn = reinterpret_cast<CButton =
*>(GetDlgItem(DlgH,gMBs.CtlBtn.Btn_ID));
gMBs.CtlBtn.m_Btmp.LoadBitmap( gMBs.CtlBtn.Btmp_ID );
gMBs.CtlBtn.m_Btmp_i.LoadBitmap( gMBs.CtlBtn.Btmp_ID_i );
gMBs.CtlBtn.m_Btn->SetBitmap( gMBs.CtlBtn.m_Btmp );
for( i=0; i<MPC_BTNS_PERSCN; ++i )
{
int b, m1, m2;
switch( i )
{
case 0: b = IDC_BUTTON1;
m1 = IDB_BITMAP_Btn_1;
m2 = IDB_BITMAP_Btn_1i;
break;
case 1: b = IDC_BUTTON2;
m1 = IDB_BITMAP_Btn_2;
m2 = IDB_BITMAP_Btn_2i;
break;
case 2: b = IDC_BUTTON3;
m1 = IDB_BITMAP_Btn_3;
m2 = IDB_BITMAP_Btn_3i;
break;
case 3: b = IDC_BUTTON4;
m1 = IDB_BITMAP_Btn_4a;
m2 = IDB_BITMAP_Btn_4ai;
break;
case 4: b = IDC_BUTTON5;
m1 = IDB_BITMAP_Btn_5;
m2 = IDB_BITMAP_Btn_5i;
break;
case 5: b = IDC_BUTTON6;
m1 = IDB_BITMAP_Btn_6;
m2 = IDB_BITMAP_Btn_6i;
break;
default: b = 0;
m1 = (b + 5)/b;
break;
}
gMBs.Btn[0][i].clks = 0;
gMBs.Btn[0][i].stat = MPC_BTN_DIM;
gMBs.Btn[0][i].Btmp_ID = m1;
gMBs.Btn[0][i].Btmp_ID_i = m2;
gMBs.Btn[0][i].Btn_ID = b;
gMBs.Btn[0][i].m_Btn = reinterpret_cast<CButton =
*>(GetDlgItem(DlgH,gMBs.Btn[0][i].Btn_ID));
gMBs.Btn[0][i].m_Btmp.LoadBitmap( gMBs.Btn[0][i].Btmp_ID );
gMBs.Btn[0][i].m_Btmp_i.LoadBitmap( gMBs.Btn[0][i].Btmp_ID_i );
gMBs.Btn[0][i].m_Btn->SetBitmap( gMBs.Btn[0][i].m_Btmp );
}
} /* do_mpc_btn_init() */
------=_NextPart_000_0058_01C9B755.51FA2160
Content-Type: text/plain;
format=flowed;
name="mpc.h";
reply-type=response
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="mpc.h"
#define MPC_SCREENS 1 /* MomPC screens of 6 buttons each */
#define MPC_BTN__SCNCTL 1 /* count of control buttons */
#define MPC_BTNS_PERSCN 6 /* control buttons */
#define MPC_BTNS_WD 180 /* button dialog dem. and bitmap dem. */
#define MPC_BTNS_HT 138
#define MPC_BTNS_BMWD 266
#define MPC_BTNS_BMHT 218
typedef struct {
unsigned int clks; /* run time count of clicks */
unsigned int stat; /* no click vs. one click stat - takes */
#define MPC_BTN_DIM 0 /* two clicks */
#define MPC_BTN_ACT 1
char name[16];
int Btmp_ID; /* default button ID */
int Btmp_ID_i; /* inverted button ID */
CBitmap m_Btmp;
CBitmap m_Btmp_i;
int Btn_ID;
CButton *m_Btn;
} MPC_BTN;
class Mpc {
public:
void do_mpc_btn_init(HWND DlgH);
void handle_btn_click( unsigned int );
private:
MPC_BTN CtlBtn;
MPC_BTN Btn[ MPC_SCREENS ][ MPC_BTNS_PERSCN ];
};
extern Mpc gMBs;
------=_NextPart_000_0058_01C9B755.51FA2160--