TORQUE_PLAYER define and file open dialogs
by Andy Schatz · in Torque 3D Professional · 07/16/2009 (2:00 pm) · 4 replies
It seems there's some weird functionality surrounding the TORQUE_PLAYER define. If it is defined (which it is by default), then it undefs TORQUE_TOOLS, which doesn't actually prevent you from opening the mission editor, but it does make any file open dialog not open (the file dialog object is surrounded by #ifdef TORQUE_TOOLS). Should I just undefine TORQUE_PLAYER in the project, or am I doing something wrong here?
About the author
#2
07/16/2009 (3:17 pm)
I'm running off trunk circa noon yesterday. 
#3
I did do some work recently on removing tools code from the binary... try putting this at the top of your project.conf
setToolBuild(false);
I haven't tried this in a little bit, so lemme know if you hit any linker errors... or other problems.
- Josh
07/16/2009 (5:43 pm)
I am not sure what you are trying to do here... the Toolbox should strip off the tools folder when packaging a deployment.I did do some work recently on removing tools code from the binary... try putting this at the top of your project.conf
setToolBuild(false);
I haven't tried this in a little bit, so lemme know if you hit any linker errors... or other problems.
- Josh
#4
07/16/2009 (6:30 pm)
I'm just building dev builds to make levels with, etc. Is there a "tools" build that my project generator should be creating? (This is why I needed help with projectGen stuff, I w2ant to make sure I'm working with the latest project defines, etc). All of the standard builds (debug, release, opt) have Torque_Player defined, which disables bits and pieces of the editor. 
Associate Josh Engebretson
There are changes to this coming in Beta 4
- Josh