[Solved] Is TRIGSTR Collecting Garbage?

[Furry Nova]

I've just been having a go at converting GUI into vJASS. Since there's a wait delay required I thought it be better using local run of temp variables instead of global ones to prevent the risk of outside trigger passing or bugs that access the same variables. After so many errors, I finally got the trigger to work.

Now I think I've found a new problem. After checking my code I've found this "TRIGSTR".

call DisplayTextToForce(GetPlayersAll(), "TRIGSTR_027")

After testing it holds the string I typed in the GUI debug messages I use for testing code flow. These can be changed into a direct string in vJASS.

If I'm correct. Every time we enter a string in actions like these below. The values are being stored in one of these TRIGSTR.

• Example
  • Events
  • Conditions
  • Actions
    • Game - Display to (All players) the text: example debug messa...
    • Game - Display to (All players) for 30.00 seconds the text: example debug messa...

Does the World Editor automatically delete the ones that are no longer used or are they always being stockpiled without us knowing? If this true is it possible to the remove ones no longer used in the map file itself, if possible with the World Editor itself?

 

[IcemanBo]

The TRIGSTR counter may increase, and you can't really avoid that, though the strings them selves don't leak: [Solved] - Do automatically generated strings "leak"?

Btw,
if you convert GUI to Custom Text, it will be normal JASS.
vJASS is JASS with a bit of extra syntax, which comes along with JassHelper tool. Elemental Coder Guide

 

[Furry Nova]

Thanks for letting me know. I was worried my debugging messages was increasing the map size.

 

[KILLCIDE]

Worrying about map size increase should be one of the last things to worry about with the new patch.

 

[IcemanBo]

In general it's easier to debug things in JASS.

But just also to know-- you're technicaly able to use local variables with GUI, if you shadow their global variables in custom script first.
local udg_ here is explained how to work with shadowing. For some cases it might be an easy and neat solution to work with locals in GUI, even it's not the proper way.