- Joined
- Sep 8, 2004
- Messages
- 633
I've been into Wc3 editing for quite a while already. I have finished quite some maps already. In all of those, I've been using GUI, simply because I never had the time nor discipline to learn JASS (I know basics and am learning now, but it will take a long time until I'm as good with JASS as I am with GUI).
For convenience's sake, you may assume that I use GUI the best way possible (except I don't use hashtables), I don't leave memory leaks (or just really few), I tie up all loose ends, optimize it through vexorian's map optimizer in the end etc.
Often though, when I've got a map full of GUI code, things start going wrong. Code that looks perfectly fine in the editor, just won't run at all ingame, do stuff completely wrong (again, although the code is perfectly fine), cause people to disconnect, cause the game to crash... etc.
What on earth could be the problem here? Is the GUI part coded so awfully that it causes problems like this? I know the JASS it becomes when compiling is pretty damn horrible - but this bad?
Who can tell me, what functions, combinations etc. cause the above problems on their own? Perhaps I accidentaly used something I shouldn't.
I'm getting pretty damn annoyed by the fact that good GUI code goes bad, and I'd like to find a way to fix it. Like I explained above, it'll take a huge amount of time until my JASS is on-par with my GUI, making it impossible to switch over easily.
For convenience's sake, you may assume that I use GUI the best way possible (except I don't use hashtables), I don't leave memory leaks (or just really few), I tie up all loose ends, optimize it through vexorian's map optimizer in the end etc.
Often though, when I've got a map full of GUI code, things start going wrong. Code that looks perfectly fine in the editor, just won't run at all ingame, do stuff completely wrong (again, although the code is perfectly fine), cause people to disconnect, cause the game to crash... etc.
What on earth could be the problem here? Is the GUI part coded so awfully that it causes problems like this? I know the JASS it becomes when compiling is pretty damn horrible - but this bad?
Who can tell me, what functions, combinations etc. cause the above problems on their own? Perhaps I accidentaly used something I shouldn't.
I'm getting pretty damn annoyed by the fact that good GUI code goes bad, and I'd like to find a way to fix it. Like I explained above, it'll take a huge amount of time until my JASS is on-par with my GUI, making it impossible to switch over easily.