JohnBoyMan wrote:I have never had this happen before...I haven't changed the cegui code for a long time...all of a sudden
Magic is not real.
Do ya need to delete or deconstruct cegui when you close the program>?
No. The operating system will automatically reclaim all memory. You only need to concern yourself with deleting objects if you want to minimize memory consumption during runtime and/or you are using RAII or some similar technique.
I all of a sudden get a message saying [CEGUI::ALREADYEXISTSEXCEPTION] when i click on one of my buttons.
This exception is only thrown when you try to construct one of CEGUI's singletons and an instance of that singleton already exists.
I noticed you did not post your
CEGUI.log file. This may tell us/you which singleton is throwing the exception; remember you are supposed to post this file anytime you post an issue on these forums.
You should also wrap all relevant CEGUI code in try/catch blocks so that you can catch and handle any exceptions that are thrown; for example in this case it would be useful to display the message (description) associated with all CEGUI exceptions.
Is there any particular reason why you did not simply debug and/or step into the application code yourself at the time the exception is thrown? In most cases you can look at the debug (symbols) callstack and find the issue without much trouble. And in fact we typically ask for the debug callstack when assisting users in analyzing runtime exceptions.
Unfortunately I cannot offer much more assistance, as you neglected to do and/or post information gathered from these sources. However, if you can gather this additional information we may be able to further assist you.
