Torque 3D Beta 1 Bug - not setting a canvas content causes a crash
by Michael Putters · in Torque 3D Professional · 05/02/2009 (7:04 am) · 2 replies
It's not exactly an existing bug but I'm the kind of guy who believes an engine should never crash, at least not with silly changes like this:
Taking the default new project as an example, if I add a function loadMainMenu to mainMenuGui.gui and in there not do the required Canvas.setContent(), then the engine crashes since in guiCanvas.cpp:1498 it tries to use the contentCtrl to render it, and it doesn't exist anymore at that point...
Taking the default new project as an example, if I add a function loadMainMenu to mainMenuGui.gui and in there not do the required Canvas.setContent(), then the engine crashes since in guiCanvas.cpp:1498 it tries to use the contentCtrl to render it, and it doesn't exist anymore at that point...
About the author
Associate Tom Spilman
Sickhead Games