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.
#2
I'm working with big amount of scripts in a project and the current version doesn't seem to be eating that much processor from time to time comparing to previous build.
Good job Tom and thanks!
P.S. one question - any news on Unicode support?
06/13/2007 (5:59 pm)
After some testing it seems to perform much better comparing to the previous public beta (is it was 53?).I'm working with big amount of scripts in a project and the current version doesn't seem to be eating that much processor from time to time comparing to previous build.
Good job Tom and thanks!
P.S. one question - any news on Unicode support?
#3
06/13/2007 (7:27 pm)
On the agenda for 1.2. 
#4
This may not be an issue with Torsion per say but I'm not sure what the cause of this is.
edit: Can anyone else reproduce this?
06/13/2007 (7:55 pm)
I'm using TGEA 1.01. I've noticed that pre-compile reports no errors even if certain syntax errors exist. For example, removing semicolons passes pre-compile. TGEA will crash when attempting to run a script that has syntax errors.This may not be an issue with Torsion per say but I'm not sure what the cause of this is.
edit: Can anyone else reproduce this?
#6
06/13/2007 (10:25 pm)
Ah, thanks for pointing that out Tom. From the explanation in the thread you linked to it does appear that its still broken in TGEA. Using the fix you suggest there errors are able to be generated on syntax errors again. 
#7
The particular issue I have encountered is that if I leave both 2005 and torsion running, after a few days, the find dialog (ctrl-F) will take several seconds to come up. Also, if I close 2005 and reopen it with a solution, it will load the open files in the solution very slowly. I know torsion is related to the slowdown, because if I close it and then repeat the process with 2005, the solution will load much more quickly.
06/15/2007 (10:54 am)
Hey Tom, I've noticed some performance issues with Torsion and visual studio 2005, are you aware of these and does this torsion update fix any of that?The particular issue I have encountered is that if I leave both 2005 and torsion running, after a few days, the find dialog (ctrl-F) will take several seconds to come up. Also, if I close 2005 and reopen it with a solution, it will load the open files in the solution very slowly. I know torsion is related to the slowdown, because if I close it and then repeat the process with 2005, the solution will load much more quickly.
#8
Please report back if your still seeing this behavior.
06/15/2007 (11:32 am)
@John - I can't say i've seen the specific behavior your talking about, but i use VS2003 most of the time. If you were using the original 1.0 release of Torsion or the older post 1.0 betas... there were some gdi handle issues. So yes i've fixed that.Please report back if your still seeing this behavior.
#9
06/15/2007 (12:52 pm)
I was using 1.0.852 final...I'll download the beta to see if it still happens
#10
06/15/2007 (1:12 pm)
@John - Oh yea... that should be fixed then.
#11
06/17/2007 (7:53 pm)
This is really a very minor issue but it seems that the "Scroll left" and "Scroll right" arrow buttons (the two triangles right next to the "X" close button to close an individual opened file) do not do anything. It would also be really convenient to be able to click on the tab of an opened file and drag that around to re-arrange them.
#12
06/17/2007 (8:27 pm)
@Matt - Bah.... i somehow broke it. Thanks for reporting it.
#13
Those arrows are only for scrolling the bar when you have more files open than can fit in the window. Since i don't disable them they sort of imply a different behavior. I'll correct that in the next release.
06/17/2007 (9:05 pm)
Ok... its not broken... just confusing.Those arrows are only for scrolling the bar when you have more files open than can fit in the window. Since i don't disable them they sort of imply a different behavior. I'll correct that in the next release.
#14
The parameter highlighting is a little off for engine functions with typed args.
An engine function with an arg list of (int index, string needle) does
(int index, string needle) when entering the first arg and
(int index, string needle) when entering the second arg.
It would highlight string if there were a third arg and needle if there were a fourth.
06/19/2007 (8:41 am)
Quote:
* We finally do parameter highlighting for function calltips.
The parameter highlighting is a little off for engine functions with typed args.
An engine function with an arg list of (int index, string needle) does
(int index, string needle) when entering the first arg and
(int index, string needle) when entering the second arg.
It would highlight string if there were a third arg and needle if there were a fourth.
#15
... and more. So i need to make a pass trying to correct for these other cases, but we'll always have some weirdo function that doesn't obey these standards and doesn't work properly.
What i'd like to see is a more concrete standard in the official Torque code base for how these are defined including usage docs on the function, return type, and each parameter. If it was better defined i could make it much more useful.
06/19/2007 (9:29 am)
@Ben - Yep... i need to clean that up a bit... but i can't make it perfect. Torque has few standards when it comes to the function comments where the parameter list is kept. You see a few different patterns...function Object::function( %val, %foo, %bar ) void Object::function( var, foo, bar ) Object::function( int var, int foo[, string bar=1] )
... and more. So i need to make a pass trying to correct for these other cases, but we'll always have some weirdo function that doesn't obey these standards and doesn't work properly.
What i'd like to see is a more concrete standard in the official Torque code base for how these are defined including usage docs on the function, return type, and each parameter. If it was better defined i could make it much more useful.
#16
06/19/2007 (1:13 pm)
I'm with you on that one. I'd like to see a better standard for the function help too. I've been using a pretty consistent format based on doxygen style syntax for things I've worked on.
#17
06/19/2007 (1:22 pm)
@Ben - Your our inside man now... make it happen! ;) 
#18
In just about every editor I've used (on windows platform, netbeans, eclipse, vc, OOo, text editors) it works similar to Ctrl+X, but in torsion it just deletes the line the cursor is on.
Sorry for the post if this was mentioned as a bug somewhere else in the forum.
06/20/2007 (1:32 pm)
Is Shift+Delete not supposed to work like Ctrl+X?In just about every editor I've used (on windows platform, netbeans, eclipse, vc, OOo, text editors) it works similar to Ctrl+X, but in torsion it just deletes the line the cursor is on.
Sorry for the post if this was mentioned as a bug somewhere else in the forum.
#19
06/20/2007 (1:58 pm)
@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.
#20
06/21/2007 (3:46 am)
Thanks! :) I'm so used to shift-delete and having my code disappear each time I used it was not cool. 
Associate Fyodor -bank- Osokin
Dedicated Logic
huge thanks!