Subclassing controls in a class

I'm having a similar problem to the one that originally stumped me with regards to defining a non-static windows procedure method within a class. This time the problem relates to Subclassing.

I am attempting a similar solution, i.e. when I create the control, I am passing the "this" pointer as the LPARAM, so I can avoid having a purely static procedure for the control.

The problem I am having is that the SetWindowLong API function wants a LONG as the third paramater, but I am unable to cast the method to a long.

Code:

---

OldCtrl = (WNDPROC)SetWindowLong(buttonCtrl, GWL_WNDPROC, (LONG)ButtonProc);

---

i.e. the above is generates a compiler error.

Quote:

---

'type cast' : cannot convert from 'LRESULT (__stdcall CApp::* )(HWND,UINT,WPARAM,LPARAM)' to 'LONG'

---

Any ideas?

I think what you want is SetWindowLongPtr which is defined as

LONG_PTR SetWindowLongPtr(
HWND hWnd,
int nIndex,
LONG_PTR dwNewLong
);

Nah, it gives you the same error only saying it can't convert to LONG_PTR.

Are you sure? Your supposed to be casting to a LONG_PTR here not a long. C++ allows you to cast to any point time with the reservation that you have a pointer type.

It is impossible to do what you're trying to do.

No amount of casting is going to work.

Okay - so it is best to use a global control procedure?

Use one of the many solutions provided here.

gg

Thanks Codeplug, but I have read those and have tried to implement the approach that I feel most comfortable with and was completely snookered by the fact you can't cast a class method to a LONG or LONG_PTR. This is most likely a problem of lack of knowledge with C++ (duh!).

Let me try another approach. I don't need any code - just an opinion, I know there are always many different ways to achieve something, and I have acheived this using at least two methods that were listed in the other post. But I don't like both of them, because they require shed-loads of static class members.

How do those that program using OOP constructs generally subclass their controls within a class, while trying to adhere to OOP principals (i.e. data encapsulation, polymorphism etc)?

They use one of the options you've most likely already read about in previous information.
Perhaps a better understanding function pointers and how they relate to class member functions will help.

gg

It probably will. Thanks I will read.