Pyro wrote:That's neat! :shock:
Thanks.
Pyro wrote:As Ben said (I think), could this also be done for vehicles too? For example, the "Z-Type" car is actually "VTYPE" in the scripting (along with loads of other names for cars). Of course, it would need to detect various typing/capitalisation of commands, such as:
...
And so on. Each of those would turn into "VTYPE" for coding purposes. As you can see, there are a lot of cars and even more names!
Seems like
easy peasy japanesey. Because i work basically only with lowercase tokens.
I convert them all to lowercase, so it will not matter for the parser if it's like you said:
ztype, Ztype, ZType, ZtyPe, for parser, they are all the same.
Actually "z type" is incorrect, because of the space. I should ignore that because it's user's fault not mine. miss2 will complain anyway.
I could maybe fix small user typos, but if it's gonna be a spell checker then it will take forever to finish the editor.
PS - The things I look up constantly are the remap colours of characters and cars, would it be possible to do some sort of palette? Again this is just convenience more than anything. Even if it's a separate window for reference it'd be cool (such as View -> Remaps or something).
TM posted nice image, if he allows to use it, then i could include it. Maybe even in help file.
It's a bit BIG but maybe modified if i recreate it with TM editor.
Edit - I just noticed in your animation you forgot to type in the min and max delay for the generator :P
I know, i was in a hurry and actually it was only to show that i got it working.
Also, with this method of "auto correction", is it done after pressing space or enter? I would assume after pressing space so you could actually type in the timers.
Yes, space.
But i have to solve one (hopefully) problem with them. There could be more or less spaces before and after the commands. At the moment i assume that there is only one space between each command and brackets, etc...