ascottk on 30/3/2005 at 06:39
I've been having a lot of problems with the triggerscript browser. Lately it's been nothing but a headache and I have to force quit T3Ed. The browser's been stealing focus so I can't save my map and the main T3Ed screen doesn't refresh. Hell I can't even minimize the editor.The triggerscript browser is slow opening, it's slow on save & refresh, and then it does a build-all on my map. That's when the browser goes haywire. Is there a better way of working with scripts? There's check-in check-out options and I have no idea what they do (if they do anything).
Mandrake on 30/3/2005 at 07:04
Quote Posted by ascottk
I've been having a lot of problems with the triggerscript browser. Lately it's been nothing but a headache and I have to force quit T3Ed. The browser's been stealing focus so I can't save my map and the main T3Ed screen doesn't refresh. Hell I can't even minimize the editor.The triggerscript browser is slow opening, it's slow on save & refresh, and then it does a build-all on my map. That's when the browser goes haywire. Is there a better way of working with scripts? There's check-in check-out options and I have no idea what they do (if they do anything).
My guess is that the check in and out options are part of the network source control system ISA used, so probably won't work with a standalone editor.
The first time you open it after opening a map, its reading all the scripts to generate the list you see - on my machine this takes about 10 seconds, and if I close the browser (using cancel) and open it again I don't get another 10 second delay.
The trick to realise is that if you press OK, or Save and Refresh,
or click the top right X close button, then it will compile
ALL the scripts. This takes a long time... even on my P4 2.4Ghz with 1GB ram it takes well over 2 minutes. It's normal for it to take a long time to compile all the scripts, during which the program appears to have frozen, and counter to normal windows interface design the X close button in the top right does the same as the OK button
not the CANCEL button. :tsktsk:
There isn't any way that I've found to just compile changed scripts, so its VERY important that if you're using the Trigger script browser to browse through scripts, or select scripts for actor properties (by clicking the .. button in an actors Properties->Script line etc) that you always use CANCEL to exit the browser, UNLESS you have actually created a new script or edited one.
Using cancel whenever possible instead of clicking on OK or X will save you a world of grief... :thumb:
Another tip is that if you actually ARE editing scripts and you're experimenting (like me) on lots of variations of a similar theme to try and find something out by trial and error, its actually much faster to create each possible version of your script at the SAME time, and call them myscript1 myscript2 and so on, then click OK to compile all scripts ONCE, then you can quickly change WHICH script your actor is using by editing its properties, which is a fast process.
When you're happy with which version of the script works properly you can dispose of the others...
ascottk on 5/7/2005 at 02:20
:mad:
The Trigger Script organizer file got corrupted. Anyone else have that problem? I compiled the scripts & I get a Viktoria Message. The ScriptOrganizer.tso was down to 1 kb (normally 45 kb). It started happening & I'm thinking my tweaks to the T3Ed.exe might be causing it.
Well, I only have those probs if the script is in the map I'm working on. When I have no map loaded it's fine :confused:
EDIT: It seems like it was my latest *.exe tweak, now fixed.
Bumbleson on 5/7/2005 at 23:43
I also had a few problems with errors while working with the TS browser, especially when it compiles the scripts, but it never actually corrupted anything (at least not that I know of). A restart of the editor always fixed things for me.
Judging by some comments I found in various files, the check in and check out options, which appear in some other editor sections too, allowed the devs to remove certain portions of data temporarily (or at least to mark them as "checked out"), probably to prevent accidental changes by other devs on the network while one was debugging the code, or something to that extent.
Crispy on 6/7/2005 at 12:48
Yeah, "Check in" and "check out" are phrases used in source control systems. The buttons are definitely a remnant of whatever source control system Ion used; and are therefore completely useless to us.
Basically, before you're allowed to start changing something, you have to "check it out". Then you make your changes. While you're doing this, nobody else is allowed to "check out" the file; therefore they're not allowed to change it either. This prevents multiple people making conflicting changes and ending up overwriting each other's work. When you're done, you "check in" the file. Your changes are saved on the server, for all the other devs to access. Anyone else who wants to change it can then "check out" the file again, and the process repeats.
(The above isn't quite true; most source control systems are smart enough to usually allow multiple people to edit the same file, and merge the changes into a master file when all of those changes are checked in. Occasionally human intervention is required if the changes conflict directly, but often the software can figure it out.)
As a sidenote, is it actually necessary to compile the scripts? I've never had a problem with scripts when I press Cancel all the time; the changes seem to save anyway. At least when testing from the editor (including using Send to Xbox).
