Questions about removing statically managed window names
Posted: Tue Jul 26, 2011 04:28
I noticed changeset 2520 removes statically managed window names and associated functions such as WindowManager::getWindow():
I'm curious about the reasoning behind this.
Also, what is the new way to accomplish tasks originally done with WindowManager::getWindow()? For example:
- Load a window layout twice (for instance: VanillaConsole.layout), then set/get a property on one of those windows or their child-windows.
- Load a window layout from C++ CEGUI, then modify the resulting windows from Python PyCEGUI.
MOD: Initial iteration of code to remove statically managed window names. This basically means that WindowManager can create multiple windows with the same name, although it also no longer tracks windows by name (so WindowManager::getWindow and such functions are removed).
I'm curious about the reasoning behind this.
Also, what is the new way to accomplish tasks originally done with WindowManager::getWindow()? For example:
- Load a window layout twice (for instance: VanillaConsole.layout), then set/get a property on one of those windows or their child-windows.
- Load a window layout from C++ CEGUI, then modify the resulting windows from Python PyCEGUI.