Guido Kohlmeyer wrote: > Meanwhile I found huginApp::Get()->GetXRCPath(), which is the same.
is there a reason to have twice the same thing, or is this a redundancy? if it is, from which class does it make sense to get the XRCPath? from huginApp.h or from MainFrame.h? huginApp is used in: ./src/hugin1/hugin/CPImageCtrl.cpp ./src/hugin1/hugin/MainFrame.cpp ./src/hugin1/hugin/PreviewPanel.cpp MainFrame is used in ./src/hugin1/hugin/CPListFrame.cpp ./src/hugin1/hugin/PreferencesDialog.cpp ./src/hugin1/hugin/CPEditorPanel.cpp ./src/hugin1/hugin/ImagesPanel.cpp ./src/hugin1/hugin/PanoDruid.cpp ./src/hugin1/hugin/AssistantPanel.cpp ./src/hugin1/hugin/GLPreviewFrame.cpp ./src/hugin1/hugin/RunStitcherFrame.cpp ./src/hugin1/hugin/PreviewFrame.cpp ./src/hugin1/hugin/ResetDialog.cpp I am inclined to say that it is OK the way it is: huginApp is used in the three windows that opens, of which MainFrame is one of them. And MainFrame is used within all the file that make the MainFrame tabs. Or am I missing something? > Dealing with simple char buffer in the code pattern > seams obsolete, cause wxString and string are available. As far as I understand this (correct me if I am wrong), this is just about determining a file name for the celeste model and loading it. I guess Tim has chosen the code pattern because it is simple, it can be used in both the standalone and the wx/GUI version, and it does the job. Or am I missing something? Yuv (still on the learning curve as far as C++ and wxWindows goes) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
