@Rackle,
Nice job!
I have an observation.. I do not load all the windows at once. They are loaded on the fly as the user needs them (once loaded, they stay loaded). From what I can tell, the current implementation loads the saved dialog data once and attempts to set all the defaults at that time. It would be nice to have the ability to call the class and say
setConfiguration( <supply window name or pointer> ) so that it can be called at anytime.
Another idea would be to have another implementation that would use class inheritance. I say this because one usually writes a class implementation about a window. For example, someone may have a
configuration.layout and have a class called
CConfiguration to manipute the window, it's data, etc. So, I could see something like:
Code: Select all
class CConfiguration : private CDialogConfiguration
{
// Class now loads its own dialog configuration from a profile
..
}
BTW, you may want to rename it from
DialogConfiguration to
WindowProfile and submit it as an enhancement to CEGUI. It would be something everyone would use. Then, if we can, we convence CE to make it part of the
CEGUI::Window class so that any user can do something like:
Code: Select all
CEGUI::FrameWindow *mFW;
...
mFW.loadWindowProfile( "<file.profile>" );
...
mFW.saveWindowProfile( "<file.profile>" );