I'll try looking at improving the autocomplete.. Should be pretty simple if I write my own instead of using the one from the text box library.. So far I have been focusing on catching the rest of the errors, but I think I got that done, so I'll start looking at a new autocomplete system.. tomorrow :)
What do you mean the autocompletion should include functions and parameters? It does include custom functions/locals/globals/structs. It will need to parse the imput before it can show the custom functions though. If you loaded the default skeleton, the program will parse everything, to collect all defined methods, structs, fields and locals. Everything includes whatever you included, such as NativeLib.galaxy, aswell as everything included in that file and so on. Parsing all that does take some time. After includes have been parsed, they get cached though, so next time you change your code, it wont parse includes again.
In the version im working on now I added a status bar to tell you how far it has come parsing the code - hope that helps once I release it.
Also, I might put parsed versions of the default libraries on the disc, so they wont need to be parsed at all.
By all means, keep bitching :)
I'll try looking at improving the autocomplete.. Should be pretty simple if I write my own instead of using the one from the text box library.. So far I have been focusing on catching the rest of the errors, but I think I got that done, so I'll start looking at a new autocomplete system.. tomorrow :)
What do you mean the autocompletion should include functions and parameters? It does include custom functions/locals/globals/structs. It will need to parse the imput before it can show the custom functions though. If you loaded the default skeleton, the program will parse everything, to collect all defined methods, structs, fields and locals. Everything includes whatever you included, such as NativeLib.galaxy, aswell as everything included in that file and so on. Parsing all that does take some time. After includes have been parsed, they get cached though, so next time you change your code, it wont parse includes again.
In the version im working on now I added a status bar to tell you how far it has come parsing the code - hope that helps once I release it. Also, I might put parsed versions of the default libraries on the disc, so they wont need to be parsed at all.
Every time I start making a map, I get too fustrated with the custom script editor, so I decided to make my own.
It has features like syntax highlighting, autocompletion of keywords aswell as stuff defined by the user, and it reports errors
Hope someone other than me can find it usefull.
http://www.sc2mapster.com/assets/beiers-galaxy-script-editor/
If you find any bugs, or have a suggestion for extra features, please post about them ;)