Asserts on isAwake() in GuiControl
by Tom Spilman · in Torque Game Engine Advanced · 03/03/2005 (9:20 pm) · 2 replies
I originally posted this on the TGE Engine forum, but i'm suspecting this is a TSE issue only.
I've been running TSE in debug alot lately and have consistently gotten several AssertFatals from the GuiControl class when i use the mission editor. The particular lines are 135, 361, 378, and 390 (all are test for the awake state of a control). These never fire in release... only in debug, so for now i've just commented them out to keep them out of my way.
I'm using HEAD from 12-27-2004.
I've been running TSE in debug alot lately and have consistently gotten several AssertFatals from the GuiControl class when i use the mission editor. The particular lines are 135, 361, 378, and 390 (all are test for the awake state of a control). These never fire in release... only in debug, so for now i've just commented them out to keep them out of my way.
I'm using HEAD from 12-27-2004.
About the author
Tom is a programmer and co-owner of Sickhead Games, LLC.
#2
Well maybe this isn't so strange... is TORQUE_ENABLE_ASSERTS defined for debug builds in the project file in CVS? I seem to remember adding it myself at some point. Maybe no one has tried it?
03/04/2005 (9:53 am)
Yea i confused AssertFatal() with the AssertISV() macros.Well maybe this isn't so strange... is TORQUE_ENABLE_ASSERTS defined for debug builds in the project file in CVS? I seem to remember adding it myself at some point. Maybe no one has tried it?
Torque Owner Markus Nuebel
This can only mean, that onWake hasn't been called before, but this seems to be really strange.
BTW: Assert are not compiled into the release version, so that's why you get them only in a debug version.
-- Markus