After several hours of attempting to recode the MessageMap functions whose names are no longer consistent with the code, I gave up. Too bad. This seems like a useful project if someone wanted to make the effort to update it.
Like a lot of people on this post, I've tried to convert the project to VC8. I've managed to fix all the handlers and messages that have changed from VC6 but I'm stuck with a problem: window messages such as ON_WM_CREATE or ON_WM_CLOSE are not accepted for CCmdTarget-derived class (see the PIMDITabs project, CMFPlugin class).
I don't understand why it is working for VC6 and not VC8. I've had a look around but could not find any information.
I guess this project is outdated. The issue seem to be the MessageMapFunctions which hasn't got the same method names nowadays. If you have enough knowledge to call the new correct methods from CPlugInApp::DispatchCmdMsg I guess it will at least compile but then if it will work is another question. Too bad, it seem to be a very clean and simple solution though.
Did you ever find a solution to making this neat plug-in manager project compile and work with VS2005 or VS2008? I am thinking about incorporating it into a large MFC based open source program, but like everyone else, I have discovered that MFC has changed significantly in these newer compilers. If anyone knows how this turned out, please let me know. Even if you didn't find the total solution, if you will send me the updates that you mentioned, I will at least start from there.
First of all great article, I've been playing around with it a bit and it's really cool. However I do have a couple of questions regarding the implementation of documents:
1. Would the inclusion of a Rich Edit Document format be that difficult to include in the plug in library? I know you would have to derive a class from CRichEditView and CRichEditCntrItem, but would the whole OLE thing be difficult to handle?
2. How do the custom document classes in the plug in library effect the DECLARE_SERIAL macros?
is there anybody have a vc++.net 2003 or 2005 version ?
i can not build the pluginlibrary project in vs2005.net
can you help me? or give me a new version.
my email:email@example.com or firstname.lastname@example.org
Do you have an example of how to implement the GetDLLDocTemplate, GetDLLDocTemplateCount and ReleaseDLL. functions. I'm looking at trying out your plug-in concept by placing a template into a DLL. But I'm having some trouble figuring out how I should go about implementing these functions.
By the way I have managed to update your library to use it in VC7, it took some work but I can now get it to compile. Still have a few minor bugs to work out.
Anyway, any help you can provide would be greatly appreciated. I don't need a full example just some psudo code to get me started.
Can anyone give me some ideas why I can't get a merged menu to be active?
I think I just need some fresh eyes on this one. I am able to insert the menu resource but can't seem to get it enabled.
I am just trying to learn the library and I have inserted the ID_VIEW_VIEWOPENDOCUMENTSTABBAR and have message mapped it but I can't seem to get it enabled to support functions from within the .dll. I am not trying to insert any toolbars though just trying to test it with a AfxMessageBox.
I tried to extend my PlugIn App with a new CMyMultiDocTemplate:
extern "C" CMyMultiDocTemplate* GetDLLDocTemplate(int index)
pTemp = new CMyMultiDocTemplate(
well this code works ... you can create a new window etc. but when you close the app the DocManager seems to be unable to delete the pointer to the DocTemplate and crashes the app. Why?
I have an SDI Application working with the singleinstance DLL, and I have a CPIDoc/CPIView DLL that compiles without error but I'm not exporting the DOC/VIEW properly.... I don't get the new view in my app....
Can you PLEASE, PLEASE, PLEASE provide a "quick" overview of getting the Doc/View exported correctly ?
How do you do? I am a Art software designer whom lives in China. I like your job very much. Can you tell me how could your work be changed into SDI program. I try to do this, but it would not work.
I work on OpenGL programming.
Call me Jian
I am loking forword to hearing from you
There is a reason for this. As the plug-in may be acting for several different objects, the plug-in may need to keep state information about the class object it is working for. If you used the same object for all the objects it plugs into, then you may be over writing the state of one class plug-in with another.
If that makes sense.
BTW, the new single instance plug in in coming very shortly. It requires a minor upgrade to the main article. I am in the process (as we speak even) of typing up the article and making sure all the source is in order.
Roger Allen - Sonork 100.10016 Strong Sad: I am sad I am flying Who is your favorite Strong?
Last Visit: 31-Dec-99 19:00 Last Update: 27-Feb-24 10:10