Z.K. wrote:
Sgt. York wrote:
Z.K. wrote:
I had to put my gotSensor outside of my class to make it work. If I
put it in my dialog header file I get the following error:
error C2276: '&' : illegal operation on bound member function expression
How do I make this work inside the class or how do I access a control
on the dialog form from outside the class. It works fine in a Win32
console application, but I need to convert it to a MFC program.
Z.K.
//////////////////////////////////////////////////////////////////////////
//outside of class
int __stdcall gotSensor(CPhidgetInterfaceKitHandle phid, void *meh,
int ind, int val);
void CTestWin32PhidgetDlg::OnBtnSensor()
{
// TODO: Add your control notification handler code here
int something;
CPhidgetInterfaceKitHandle ifkit;
CPhidgetInterfaceKit_open(&ifkit,0,-1);
CPhidgetInterfaceKit_set_OnSensorChange_Handler(ifkit,&gotSensor,
&something);
while(1)
{
CPhidgetInterfaceKit_read(ifkit);
}
}
//outside of class
int __stdcall gotSensor(CPhidgetInterfaceKitHandle phid, void *meh,
int ind, int val)
{
CString temp;
temp = "hello";
//AfxMessageBox("hello");
return 0;
}
Declaring your member function gotSensor() as static, if possible,
will correct this problem (and then of course scope it properly when
you pass the address). The way you're calling it here, the function
signature, if it's a non-static member function, is not what you think
it is -- the first parameter is a "this" pointer to its enclosing class.
Okay, I got that to work with the code below, but how do I access my
member variable m_Sensor.SetWindowText("hello"). Everytime I do I get
an error specifying that is illegal to call a non-static function from a
static function.
Z.K.
static int __stdcall gotSensor(CPhidgetInterfaceKitHandle phid, void
*meh, int ind, int val);
int __stdcall CTestWin32PhidgetDlg::gotSensor(CPhidgetInterfaceKitHandle
phid, void *meh, int ind, int val)
{
CString temp;
temp = "hello";
//AfxMessageBox("hello");
//m_Sensor.SetWindowText("hello");
return 0;
}
Exactly. That's why I said "if possible," but in this case it's not, as
the compiler points out. So, you might explore the second option you
specified above. I have not seen enough code to understand the problem