Why is wc3 trigger editor soo complicated and uncompleted?

[Tinker]

Also it leaks memory if you dont remove them urself.

Sorry i just wanted to share this.

 

[Accname]

Counterquestion: Why do you try to use the editor for things the editor was not meant to do?

It is designed to create wc3 custom melee maps. Blizzard does not support the creation of complex maps with huge custom engines, the editor was not created for such a purpose. For what it is ought to do the editor is an amazingly powerful tool with many possibilities beyond its original purpose, you should rather be thankful that blizzard implemented such a wonderful toy and added it to the game for free. Not many games come with such a nice addition by themselfs.

About the memory leaks, thats the standard.
Such things as garbage collection are a luxury you wont enjoy too often. Thats a task which requires performance and memory as well and i can very well understand if the wc3 developers were trying to squeeze out as much performance as possible and managed the memory al- and delocation themselfs to improve the outcome of the product.

And its true, there are quite some bugs in the editor and even in the game itself, but then again, the editor is freeware, what do you expect?

 

[Inflicted]

@accname This thread is almost as pointless as mine. Yet i don't see sarcasm or any flaming in his direction.

There are ways to prevent many leaks, but as said before not everything is preventable.
If you dont like the default editor, there are other programs.

 

[Sim]

@ Inflicted

... don't start something that was already long overdue to be over.

Also, post #2 covers the topic quite well enough.