Torsion 1.1.130 Beta
by Tom Spilman · in Torsion · 06/11/2007 (2:26 am) · 58 replies
Hey guys and gals!
Got a new beta build up tonight for everyone. This is basically the 1.1 release candidate... so hammer on it and report as many bugs as you can.
Torsion TorqueScript IDE 1.1.130 Beta
A bunch of changes in this build...
Seems all the GDI issues are gone now as i've gotten no reports of slowdowns or corruption from the last build.
Also this build had some big changes in how the Torque EXE is launched to work with to forthcoming TGB 1.5 release candidate. Changes were made to Torsion and TGB, so until the new TGB build is out Torsion will still have issues with it.
Enjoy.
Got a new beta build up tonight for everyone. This is basically the 1.1 release candidate... so hammer on it and report as many bugs as you can.
Torsion TorqueScript IDE 1.1.130 Beta
A bunch of changes in this build...
Quote: * Config dialog changed to show full path.As usual be sure to post bugs to our mantis bugtracker.
* Config executables are no longer assumed to be absolute paths (fix for TGB 1.5).
* We now delete the output.log before generating exports to avoid duplicates.
* Fixed incorrect cursor position when hitting up arrow after closing curly bracket.
* You can now set the global variable color differently from local variables.
* Disabled the use of File->Save As to rename the active project.
* TorqueML commands are now properly escaped in the output window and tooltips.
* Enhanced ScriptSense completion on ( and = defaults to off and is toggleable in preferences.
* We finally do parameter highlighting for function calltips.
* Parameter info properly removes %this from the calltip for member function.
* You can now configure calltip colors in the preferences dialog.
* Fixed selection copy when pressing ctrl before clicking and dragging.
* Major refactor of how the debugger launches EXEs to work with TGB 1.5.
* External Tools can support commands that use the global AppPaths registry key.
* You can now get calltips for globals outside of the current breakpointed function.
* Refactored ScriptSense database shutdown to hopefully resolve shutdown crashes.
* Fixed bug where member functions were evaluated as variables in debugger calltips.
* Watch window updates now display evaluation error messages.
* We no longer send watch variable updates on value edits that do not result in a change.
* Fixed bug where Find dialog could be stuck offscreen.
* Fixed performance problem when watch window would clip a very long string.
* We no longer show calltips for globals without a description.
* We will now open associated applications when launching a file from the Find Results window.
* Fixed bug where editor focus was not set when right clicking and ctrl+left clicking.
* Fixed crash bug when using Ctrl+Shift+F4 to close all documents.
Seems all the GDI issues are gone now as i've gotten no reports of slowdowns or corruption from the last build.
Also this build had some big changes in how the Torque EXE is launched to work with to forthcoming TGB 1.5 release candidate. Changes were made to Torsion and TGB, so until the new TGB build is out Torsion will still have issues with it.
Enjoy.
About the author
Tom is a programmer and co-owner of Sickhead Games, LLC.
#22
06/21/2007 (12:20 pm)
@Guimo - Look in Torsion preferences. I added an option for toggling "Enhance ScriptSense" which you can use to disable completion on ( and ,. In the next release i'll also put in an exception for ( completion on the 'for' keyword. 
#23
If no text selected Shift+Del works the same as selecting whole line and cutting it into clipboard.
If some text selected Shift+Del works the same as usual Ctrl+X - cut selected text into clipboard.
06/22/2007 (9:01 am)
@Tom:Quote:@Leslie - Yea it seems Visual Studio also has Shift+Delete acting the same as Cut. It is either a bug or someone specifically asked for it to be different and convinced me to change it... i honestly don't remember. In this case since VS does it... i'll fix Torsion to match.That can be a bit confusing... but it "should" work like this (and working in VS):
If no text selected Shift+Del works the same as selecting whole line and cutting it into clipboard.
If some text selected Shift+Del works the same as usual Ctrl+X - cut selected text into clipboard.
#25
In any case, I do have one request:
Short version: Create tab for listing all errors on precompile / run together
Long version:
Right now when an error occurrs during a precompile or run the line is usually highlighted in red and with a marker in the scroll column to the right indicating what the error was. Errors can also be cycled through using the next and previous error buttons that are provided. As it is right now the errors are usually hidden among a huge amount of other spam regarding the build / compilation / execution of the code in the "Output" tab. It would be very convenient to have a separate tab that just lists all of the errors and allows clicking on them to jump to the line in the code that was a problem.
06/25/2007 (9:58 am)
@Tom, I understand feature requests are handled on a case by case basis, but do you prefer them being introduced here in the forum or on your mantis "bugtracker" site?In any case, I do have one request:
Short version: Create tab for listing all errors on precompile / run together
Long version:
Right now when an error occurrs during a precompile or run the line is usually highlighted in red and with a marker in the scroll column to the right indicating what the error was. Errors can also be cycled through using the next and previous error buttons that are provided. As it is right now the errors are usually hidden among a huge amount of other spam regarding the build / compilation / execution of the code in the "Output" tab. It would be very convenient to have a separate tab that just lists all of the errors and allows clicking on them to jump to the line in the code that was a problem.
#26
As for your feature... thats a great idea. I have a list of a few different tabs i'd like to add, but i've been waiting for our big UI update to add them. Mostly because i didn't want to further clutter the interface without giving the user control over what tabs to display and where to display them.
06/25/2007 (10:39 am)
@Matt - Well its actually best to post here and submit it to the tracker. I usually get some great feedback from people here, but it is easy to loose a good idea here that isn't in the tracker.As for your feature... thats a great idea. I have a list of a few different tabs i'd like to add, but i've been waiting for our big UI update to add them. Mostly because i didn't want to further clutter the interface without giving the user control over what tabs to display and where to display them.
#27
06/25/2007 (11:26 am)
Sounds good Tom. I look forward to see what you come up with 
#28
06/25/2007 (12:21 pm)
I tried to cut a section of code that I collapsed (using the little +/- button) and when I pasted it, only the header portion (the part visible when collapsed) got pasted. It also created some weirdness with the other "folding" sections where the header appeared collapsed but it wasn't collapsed.
#29
06/29/2007 (6:46 pm)
Slight bug with parameter highlighting. When a function is defined purely in C++ Source the parameters are prefaced with the data type. As I enter the parameters from script it switches between the data type and then the parameter name. It seems to be keying off of the "space" character rather than the comma. 
#30
Check my post on Jun 19, 2007 08:41 and Tom's reply immediately following ;)
07/02/2007 (8:12 am)
@Mark:Check my post on Jun 19, 2007 08:41 and Tom's reply immediately following ;)
#31
07/02/2007 (9:36 am)
Ah yes, that's the one. 
#32
It also reports errors where there are none and the code doesn't match the line ie...
Which when I click on it goes to this line...(which the IDE says is line 147)...
Hmm... maybe it's the TORQUE_NO_DSO_GENERATION define in TGEA - recompiling with it commented out...
www.garagegames.com/mg/forums/result.thread.php?qt=56841
07/06/2007 (11:05 pm)
I have a problem with using Torsion and TGEA. It basically skips lines and doesn't breakpoint where it's supposed. It appears to run code without even getting to it.It also reports errors where there are none and the code doesn't match the line ie...
BRAVE/server/scripts/AI_Control.cs (147): Unable to find function AIPlayer::mountVehicle
Which when I click on it goes to this line...(which the IDE says is line 147)...
if (%targetObject.nameTag $= "Generator1")
{Hmm... maybe it's the TORQUE_NO_DSO_GENERATION define in TGEA - recompiling with it commented out...
www.garagegames.com/mg/forums/result.thread.php?qt=56841
#33
Please provide a fix... I don't know why Torsion is skipping code.
Also the comment before about the syntax error jumping to the wrong line still happens.
07/07/2007 (5:31 am)
Oh well it didn't fix it. Here's an example. I set a breakpoint on the first line, and it jumps to the third line...%enemyVehicle = Machines::spawnFlyingVehicle(%localname,%targetObject); <- breakpoint is here %enemyVehicle.mountable = true; %enemyVehicle.setEnergyLevel(60); <- jumps to this line
Please provide a fix... I don't know why Torsion is skipping code.
Also the comment before about the syntax error jumping to the wrong line still happens.
#34
07/07/2007 (5:42 am)
Here's more. I wrote some echos out to see what TGEA was doing compared to Torsion. You can see in the Output window, it does get through my code, but at 1) it returns from the Machines:: method and Torsion jumped up to the previous code as shown with the arrow in the left hand column. Actually that code is not being run at the time, as the echos prove it's actually further down. This make debugging very difficult. It's buggy. Is there a fix.
#35
07/09/2007 (7:24 am)
So I can't find a solution for this. Is this a known issue with TGEA and Torsion, because it basically makes debugging impossible at the moment.
#36
07/09/2007 (7:55 am)
I've been using Torsion with TGEA for awhile now and I haven't encountered anything like that. The only time Torsion did strange things with jumping lines and such was when I had DSO generation off and there were errors in my scripts.
#37
07/09/2007 (9:24 am)
@Andy - I think this is the block comment bug in the TorqueScript parser. Do you have any /* */ comments anywhere above this code? I posted a fix for this more than a year ago and the code made it into CMDscan.I in TGEA 1.01, but they forgot to rebuild CMDscan.cpp.
#38
07/09/2007 (9:17 pm)
Yes I did have a block comment above that. Where is CMDScan? In TGEA or the Torsion source? If in the Torsion source, where can I get that?
#39
07/09/2007 (10:28 pm)
@Andy - It's part of the TGEA source code... code/console/CMDScan.cpp i think.
#40
07/10/2007 (6:17 am)
Excellent thanks Tom - works beautifully. 
Torque 3D Owner Guimo
There is a script function called forceUpdateBing().
When I try to write a for loop and press the ( , torsion automatically selects the forceUpdate function. When I debug I find something like:
forceUpdateBind(%i = 0; %i<50 %i++) {
code code code
}
Is there any way to solve this?