e601bb9cc3
graphics context and link it with a slave camera. I don't know the reason we perform like that, which will cause a problem that the GUIEventHandler may not obtain correct window coordinates because the main camera will use a default input range to receive events from the slave camera's graphics context. It is also weird to see the addSlave() used in non-cluster applications, which beginners will be confused with. I've make a slightly modification to the osgviewerMFC example to make it work without setting slave cameras. I've tested with the MDI framework and everything seems fine." |
||
|---|---|---|
| .. | ||
| res | ||
| ChildFrm.cpp | ||
| ChildFrm.h | ||
| CMakeLists.txt | ||
| MainFrm.cpp | ||
| MainFrm.h | ||
| MFC_OSG_MDI.cpp | ||
| MFC_OSG_MDI.h | ||
| MFC_OSG_MDI.rc | ||
| MFC_OSG_MDIDoc.cpp | ||
| MFC_OSG_MDIDoc.h | ||
| MFC_OSG_MDIView.cpp | ||
| MFC_OSG_MDIView.h | ||
| MFC_OSG.cpp | ||
| MFC_OSG.h | ||
| ReadMe.txt | ||
| Resource.h | ||
| stdafx.cpp | ||
| stdafx.h | ||
This project is a very simple implementation of the Microsoft Multiple Document/View Architecture. The only changes needed to compile the project should be to modify the include paths for headers and librarys. This project was written to show how to implement the new osgViewer library with MFC. There is only one problem that I have seen to this point and that is when you have multiple OSG documents open and then you close one of them then all remaining OSG documents quit rendering. I have a small work around in the code that calls AfxMessageBox when the closing windows tread exits and this keeps the other windows rendering correctly. Not sure what the problem is at this point so if anyone finds the cause and has a fix please update the code.