memcpy Thought about this one but that would require us to cast to void*. He's saying we cannot use c-style casts too.

So it should concern us only if we are dealing with COM? May be I should have rephrased that as: "We don't need to worry if we are just exporting a class."

CPallini wrote:

Wonderful.

Q:When I export a class in a DLL, I'm not actually dealing with dllmain or those DLL_PROCESS_ATTACH , DETACH thing. I just simply export it as a class. Then how things work without implementing these? A:That depends. If, for example, your DLL was using COM and your host wasn't, it wouldn't work if you didn't handle the thread attach event and initialize COM. All the COM calls would fail because that's how COM works. So it depends on what you are doing in your DLL. In other words all DLL's are not equal. Q:So it should concern us only if we are dealing with COM? *:Really? That's your interpretation of my post? What's there for you to wonder so much? Don't expect everybody to know everything. I haven't worked with COM. That's why I asked the question that way. I found his reply a bit rude. Now yours is a bit worse. If Cedric Moonen can get question my right why can't you?

led mike wrote:

In other words all DLL's are not equal.

I just asked I should take care of dllmain when I'm writing a simple C++ exported class. And you replied with reference to COM! That was little vague or may be I couldn't follow your language. That's why I asked the question again but anyway Cedric moonen got it quite right.

Thanks! This is what I asked. Excellent. Straight forward & a neat reply.

modified on Wednesday, April 1, 2009 2:36 PM

ok :)

your DLL was using COM and your host wasn't, it wouldn't work if you didn't handle the thread attach event and initialize COM. You mean "if my DLL is a COM dll" and the hosting application not using COM?:confused: I'm really not able to follow you. Can you explain a bit more without taking out the stick?

So it should concern us only if we are dealing with COM?

Why? what's really wrong? I don't find any. May be he's not assigning any value?

How to make Matrix Using C If C doesn't fit your budget, you could contact Keanu reeves.

Come one level out from the current folder. You will again find folders named "Debug"/ "release". Your DLL will be relaxing there.

When I export a class in a DLL, I'm not actually dealing with dllmain or those DLL_PROCESS_ATTACH , DETACH thing. I just simply export it as a class. Then how things work without implementing these?

Okay I'll check them up. Thanks for your responses.

Thanks for your reply Stuart.

Stuart Dootson wrote:

Add your WM_KEYDOWN handler and add this PreTranslateMessage override and you should be good, so long as your dialog is modal:

I could rather manipulate that the key in pretranslate() itself right?

Stuart Dootson wrote:

Probably because the control with focus is getting the messages, not the dialog.

That was my guess, Just to test that I tried deleting all the controls on the dialog. Just a plain dialog but still it's not getting the event. What could be the reason here?

Looks like your OS lost a handler for "Space" KeyDown? Your subject looks like a train.

samuellhu wrote:

How to install the vs 2008 trial edition after download from mircosoft?

You need to stay online. It downloads from their server.

Why am I not able to handle WM_KEYDOWN on a dialog? Pretranslate is the only way? Also what's the reason the event is not getting dispatched to the dialog?

DavidCrow wrote:

Have you bothered to read the documentation? The fifth argument is the ID.

:doh: . Please excuse. That's dumb. Thanks for the reply.

Can't follow you. I'm creating the control like:

CButton\* pButton = new CButton;
pButton->Create("&ENTER", WS\_CHILD | WS\_VISIBLE,
	            CRect(0, 0, 100, 43), this, 1);

How do I assign a handler for this? I do not even know it's ID here. Little unclear.

How do I add event handler for dynamically created controls in MFC? For example a button & an onclick event.

Stuart Dootson wrote:

The SAVE message map should be in your doc class.

Oops! You are right.

Stuart Dootson wrote:

As I said, I found the serialize method is invoked when you open a different file than the one you currently have open (I saved a file called a.a then re-opened it - MFC detects that condition and doesn't re-open).

I knew my question was not clear this time.Sorry. Actually I understood what you said in your last reply. I was talking in context with the 0 size files. "Assuming I'm opening the 0 size file" and trying debugging, trying to catch the call stack. etc. Anyway helped enough already.

Stuart Dootson wrote:

CWinApp is in the MFC source - I can't remember off the top of my head which file and I haven't got enugh battery to open VMWare Fusion (I use OS X normally) at thh moment Smile Still - go into the MFC source directory and grep for OnFileOpen.

Oh! okay :) No probs. You are clever to move out of windows :rolleyes: .