|
Long answer...
The application is a CAD program, so many of the dialogs have common elements (line style selection, line width selection, layer etc.). The "Dialog" class contains functions that deal with these common elements.
Short answer...
Because that's how it was done when I inherited the code and I haven't changed it 
|
|
|
|
|
Well, the root of your problem is the multiple inheritance coupled with the ON_BN_CLICKED() macro definition static cast:
#define ON_BN_CLICKED(id, memberFxn) \
ON_CONTROL(BN_CLICKED, id, memberFxn)
#define ON_CONTROL(wNotifyCode, id, memberFxn) \
{ WM_COMMAND, (WORD)wNotifyCode, (WORD)id, (WORD)id, AfxSigCmd_v, \
(static_cast< AFX_PMSG > (memberFxn)) },
Here's an article on those pointers:
http://www.informit.com/guides/content.aspx?g=cplusplus&seqNum=142[^]
|
|
|
|
|
I've had enough of trying to fix it - /vmg /vmv FTW!
Thanks anyway!
|
|
|
|
|
 Good luck!
|
|
|
|
|
If you can't resolve the problem trying a few different things... you may have to condense some of your inheritances. A lot of them have little rhyme or reason. For example, why create a Dialog class when you can derive place all that code on a CDialog derived class, then you only have one class to inherit from.
class CMyBaseDialog : public CDialog
class GridBase
class GridDlg : public CMyBaseDialog, public GridBase
Now this SHOULD work correctly... emphasis on the should...
|
|
|
|
|
You are right the class structure is a mess...but I'm reticent to mess with it at the moment. I'll try and get something working from VS2010 first, then change it if I have to.
|
|
|
|
|
Well good luck, if you want more help, maybe set up a small project that just outlines what you're trying to do (just the skeletons of the classes, enough that we can see and compile the project, maybe squeeze it all into one or two files) and put it up somewhere. Its an interesting problem so I wouldn't mind helping.
Cheers! 
|
|
|
|
|
Pretty bad.
- Nevin Janzen
|
|
|
|
|
|
Any error is horrible, in my opinion.
- Nevin Janzen
|
|
|
|
|
Well that's a warning, not an error... its a level 1 warning though... so its considered severe.
|
|
|
|
|
There is still a chance of something going wrong.
- Nevin Janzen
|
|
|
|
|
Right. The only acceptable development method is keeping zero number of warning in the whole product. At least at the moment when the modified code is committed to revision control all warnings should be eliminated. If warnings are accumulated, it means the useful mechanism of warning is effectively off.
—SASergey A Kryukov
|
|
|
|
|
From MSDN page for WM_ACTIVATETOPLEVEL
http://msdn.microsoft.com/en-us/library/xkd95027(VS.80).aspx[^]
I got the below description:
This message is similar in use to WM_ACTIVATEAPP, but works in situations where windows belonging to different processes are mixed in a single window hierarchy (common in OLE applications).
Does anybody know where is a example/demo available that illustrate "windows belonging to different processes are mixed in a single window hierarchy"?
I googled but found almost nothing.
Thanks!
|
|
|
|
|
I would assume that this will happen when (say) Word runs its windows inside your application to deal with an embedded object?
So would apply to the windows / processes associated with any OLE object.
|
|
|
|
|
Hi All!
I am developing an OLE Object for MS-WORD. Now I meet a problem. And I hope someone can help me.
The Object I developing can be added into a .doc file. After added, it will draw a shape such as rectangle or circle etc. as the proof of existence. Now I find that when the .doc file which had been added the Object is to be loaded, the shape will be drawn twice. And the position of these shapes are different. I don't know why this occurred.
During the time I try to fix it, I noticed that the call of "CComControlBase::InPlaceActivate" is very important. Only after I call it, the loaded object can work. I think this means that one of the two shapes I see is owned by "InPlaceActivate". The other is owned of "UIActivate". But I can't find anyway to make this object is "InPlaceActivated" or "UIActivated" only.
Is there anyone could be kind to tell me the correct way to fix this problem? Thank you!
Best regards!
There is some white cloud floating on the blue sky. That's the landscape I like.
|
|
|
|
|
Hello,
We are having COM component created for 32 bit OS. May I know what precautions or steps I need to take while porting it on 64 bit OS. If possible please suggest Any book or good link.
Regards,
Happy Programming.
|
|
|
|
|
Hey guys,
I have been writing Windows apps with WTL for years but now for several years it hasn't been updated and the new Windows versions are coming out with more controls and messages and none of them are supported by WTL. What now?
Sincerely,
Peteris Krumins
Peteris Krumins
http://www.catonmat.net
Loves mathematics, physics and computer science!
|
|
|
|
|
|
Hi all!
Now I am developing an application which will use many technology about OLE. But I know little about it. I often meet the problems. When I seek the answer in MSDN, I notice that a document named 'OLE specification' is often be referenced. I try to find it. But nothing can be found through google. Is here somebody know it? If somebody know, I hope you could be kind to tell me the web-link of it, or send it to me by email. Thank you!
Best regards!
There is some white cloud floating on the blue sky. That's the landscape I like.
|
|
|
|
|
Not too difficult to find these links[^].
The best things in life are not things.
|
|
|
|
|
Thank you very much!
There is some white cloud floating on the blue sky. That's the landscape I like.
|
|
|
|
|
Question 1:
I create one CDockablePane wnd and dock it in the bottom of the parent wnd. But the default CDockablePane height is too short and I want to resize the height of the CDP. But don't find any workable method to do.
Btw, if the CDP is docked in the left/right side of the parent wnd, it works well when setting new width.
Question 2:
Another question is how to make the CDP floating when initialized. The CDP is initially docked in one side when created. But I want to make it floating after it is created in the target position and with a initial size. How to do it ?
I feel very hard to control the CDP programmatically, like floating, resizing and moving with MFC. I found one artical from MS website about docking window management programmatically. But it is for C# Winform, not for MFC.
Can anyone give help?
modified on Wednesday, June 1, 2011 5:25 AM
|
|
|
|
|
I have the following piece of code which returns the handle to the window which should receive the focus,
CWnd* pWndNewFocus = GetNextTabStopWnd(pWndCurrentFocus->;GetSafeHwnd(), iDirection);
For setting the focus to the new window, i've written the following code, pWndNewFocus->SetFocus();
Incidentally the window that is set to receive the focus is a CButton. I have an OK button which is default button and a Cancel button. OK button is dithered. So the pWndNewFocus will be my Cancel button. When SetFocus is getting called on that, i'm not able to see the focus [dotten line around the caption] on the button.
Could you let me know the reason for this error? The same code when I execute it from VC++ 6.0, the focus is correctly getting set to the button. But when i execute the code in VC++ 10, i'm getting this issue.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
