>>Is the new version in sightrange?
I don't see it.
@SFilip
Got something needed to be fix in the folding system. My code is sure contains a big scope the wraps the whole trigger code. Everytime I needed to fold the child function, i need to do it 1 by 1. Fold all does really fold all, include the big scope.
When I open the scope, everything opens again.
Auto-indent is somewhat... buggy?
It should not leave spaces if I don't type anything in that line.
It should un-indent on "endloop" and friends.
It should definitely not indent if I press enter on, for example, "endfunction" to add an extra line...
The function suggestion list disappears once you get to the parameters???
It covers the lower couple pixels of the text...
Turning off this annoying yellow "current line" "feature" is slightly un-intuitive.
One bug what I have encountered, it can reproduced easily. I' m using JNGP pack 4b I assume, with TESH version 0.7.
If you create new map, create new trigger and convert it to custom script. After that disable that trigger and save first time map (Needs to be saved twice because first map path isn' t found, JNGP thing.). When you now try to enable your trigger JASSHelper or whatever parses it starts to give error(s) on TESH commented lines:
I failed to replicate it the way you explained, but I noticed that it's caused if the first line in your trigger is wrong (one below //TESH.alwaysfold=0 in the code).
It also only happens if you uncheck Always allow trigger enable in the Grimoire menu so that's most likely the problem here.
When is it updating? The full native + bj globals.
I dont want to add the whole J file into the containing folder and replacing all the files making them some looks in blue / red / purple.
>>Are you going to add support for vJass in the syntax check?
Impossible.
vJass syntax checker requires a whole code in a map. Syntax checker of TESH only checks the code of the specific trigger, not whole map.
Interesting, GetSelectedUnit, GetTriggeringVariableName and SetUnitPointValueByType (presumably) exist as natives, but are commented out in common.j. The little script I used to grab function names from common.j probably didn't check if the line had comments...
I'll remove them in the next version.
> Is there a date for expected release for the next update?
Not really, no. I started working on it somewhat actively though, but it might take some time.
Ghan has said he has fixed this. Monovertex please confirm this fix. This was only a problem with people that had signatures in the upper levels like not the special members but the respected members.