Hashtable Issues

[Melthal]

Sometimes when I try to save a variable to a hashtable my WE crashes. Any ideas?

 

[Berb]

Which variable types, specifically?

You have to be really careful with hashtables in GUI, because some of the types that are available to be saved in a hashtable are not accessible in GUI. For example, if you try to store a Unit Pool in a hashtable it will crash when you click on the "Unit Pool" field.

Its strange though because "Ability" is a proper variable-type even in GUI, yet when I try to use the GUI hashtable function to save an Ability, it crashes the World Editor. GUI just sucks I think.

• Unit Pool
• Item Pool
• Ability
• Widget
• Event ID
• Region

Seems pretty random actually... can anybody else use the hashtable functions for these types?

 

[Dr Super Good]

Thats cause what GUI uses as an ability is nothing more than an integer.
What an ability is is an incomplete type with no real use, even in JASS.

Regions crash cause they are regions, in GUI you use Rects so do not actually use regions.

I blame the maker of GUI being so dumb that people patching his code though it was better than it was (supported those types).

 

[Berb]

I first came across this when helping someone else with unit randomization from a unit array (because unit pools are not available in GUI). Its funny because there is absolutely nothing regarding Unit Pools or Item Pools in the GUI editor, yet there are functions that accommodate them for hashtables.

 

[Dr Super Good]

Cause they exist in JASS... WC3 would be dead if only GUI was used.

 

[Berb]

Cause they exist in JASS...

Yea, I figured that much all by myself. I don't actually use GUI I use vJass with the Jass NewGen Pack. The only reason I noticed the bug was because of some "debugging" I was doing to help somebody else with their questions.

 

[Melthal]

Thanks for the replies, and I guess that makes sense. Thanks again for the help at least I know it's not the WE's fault for crashing.