Speed up working with trigger libraries in mods?

[Kalekin]

For some reason the trigger module is awefully slow when working with a custom library for a mod. When performing actions in the library window such as creating variables/functions, renaming, moving, etc. there are 2-3 second pauses for each of these common actions. I can work in the window below the library window (local scipt?) without any delays. Is there perhaps a setting I can tweak/toggle to improve my performance when working with libraries?

 

[Dr Super Good]

I do not know of any. You could try making the library local and then once it is complete exporting it as a library.

The delay is like the same problem WC3 had with the brushlist. Every change causes it to reload every library element which is computationally intensive.

 

[Kalekin]

Bleh, very frustrating. I guess it has to do with the generating the SC2Lib XML? I can't think of any other differences between the library window and the trigger window that would create such a variation in performance.

 

[Dr Super Good]

The delay is like the same problem WC3 had with the brushlist. Every change causes it to reload every library element which is computationally intensive.

By this I am refering to it rebuilding the library trees in the interface from the raw data. Especially if you have the campaign script libraries added that is a rather complex and large structure it would have to rebuild each time.

The map specific trigger window is discociated from the library window. It might suffer the same responsiveness issues but that would first require the creation of a simlar number and complexity of elements that the library panel has.