C / C++ / MFC

Re: SetWindowLong using a class member function?

17-Sep-03 1:21

Its possible with class member functions.

Try this

LRESULT CALLBACK YourClass::MyOwnWndProc(HWND hWnd, UINT msg,
WPARAM wParam,
LPARAM lParam)
{

}

and then use
SetWindowLong(hWnd,GWL_WNDPROC,(LONG)MyOwnWndProc);

"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."

Harco17-Sep-03 4:24

Harco

17-Sep-03 4:24

This is exactly what I have now.. and doesn't work.

Are you sure this is supposed to work?

Re: SetWindowLong using a class member function?

David Crow17-Sep-03 2:43

David Crow

17-Sep-03 2:43

DanglingDude wrote:
And no, I don't want to use a non-class function. I really need to know if it's possible with a class function.

MyOwnWndProc() would need to be a static member in order for this to work.

Five birds are sitting on a fence.
Three of them decide to fly off.
How many are left?

control mouse

Ta_Tee47317-Sep-03 0:22

Ta_Tee473

17-Sep-03 0:22

i want to control my mouse cursor for open "my computer"
how i do?

somebody help me , i would like to know there.

thank you very much

MFC is a STA assisted code?

vgrigor16-Sep-03 23:31

16-Sep-03 23:31

Does MFC calls is syncronized by created STA appartement?

CoInitialize(NULL) is called in App:InitInstance.

What if I choose MTA model?

To avoid blocking and reenterance behavior?
I created some threads in MFC app.

I can not create Windowless controls in CDialog than...

Is There any slution?

thanks

Jagadeesh VN17-Sep-03 0:57

17-Sep-03 0:57

If you choode MTA model, you need to call CoInitializeEx( ).

"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."

Jagadeesh VN17-Sep-03 1:11

17-Sep-03 1:11

To join the MTA of a process, a given thread must call CoInitializeEx(0, COINIT_MULTITHREADED). Any objects created within this thread must be thread-safe.

I would suggest to use the MTA model. If you implement it properly, then COM will come in and take care of synchronization for us.

After working with "Apartment", "Both", and "Free", I would take MTA anytime over STA model.

"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."

vgrigor17-Sep-03 1:25

17-Sep-03 1:25

You incorrectly inderstand my question -
I had read article you cited,

but need to esplain not how to create MTA,
but how to define precisely that MFC based on it -
is made safe.

Jagadeesh VN17-Sep-03 1:33

17-Sep-03 1:33

MFC is not threadsafe!!!

"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."

vgrigor17-Sep-03 1:49

17-Sep-03 1:49

there is an opinion where MFC is not safe for MTA,
and how to modify to make thread -safe?

Jagadeesh VN17-Sep-03 1:50

17-Sep-03 1:50

I have read some articles( yrs back ), where they have mentioned that MFC is not thread-safe, and so cannot be used with MTAs. I remeber someone suggesting to thread-safely implement IUnknown, to over come this problem. But that shudn't be enough. Why MFC cannot become MTA is still unresolved.

I think its better to remove that itching rabbit(MFC) from your code.

"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."

Jagadeesh VN17-Sep-03 1:56

17-Sep-03 1:56

Lemme search that article for you.

I'l post the URL as soon as I find it.

"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."

vgrigor17-Sep-03 1:59

17-Sep-03 1:59

My program is MFC based,
I would glad to eliminate, but what instead?

WTL is not well documented, and not standard in programming.

Jagadeesh VN17-Sep-03 2:08

17-Sep-03 2:08

Go for ATL without MFC support. If you include MFC support in your ATL project, your COM object has to start choking up around the MFC runtime DLL. But its true that, you will get all the features in MFC, But you will have to pay for it.

So I would say, its actually a design decision, which you have to take. If you have GUIs, then u may use MFC, otherwise dont go for that. Thats my advice.

"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."

vgrigor17-Sep-03 2:17

17-Sep-03 2:17

I have complex mainly GUI application, that was based on MFC,

but threading is also good thing for not to use in any library.

is there method to correctly use GUI libraries in threading environment?

Jagadeesh VN17-Sep-03 2:31

17-Sep-03 2:31

You can have dialogs ( CAxDialogImpl ) and property sheets in ATL itself. But if you want anything more, use MFC, and choose STA Apartment with 'Apartment' threading model.

Refer msdn for more details
Start here[^]

"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."

Anonymous18-Sep-03 3:30

Anonymous

18-Sep-03 3:30

You may not have to worry if MFC is thread safe.

You can use multi-threading with an MFC application as long as you always use the MFC stuff from the main thread. What are you using multi-threading for? If you just need working threads to do some calculations in the background without directly touching the UI, you can do that fine.

vgrigor18-Sep-03 3:37