Unit Indexers questios :S

[alexmantor]

Duo to they are confusing I got to ask some stuff....

1. They replace the hashes? (I mean a way to use the same trigger for different units at the same time)

2. HOW THE HELL I USE THEM? (They are filled with lots of code a vars and that confuse me)

3. Whats the best one I can use?

4. if I've created hashables to use my triggered spells or give diferent orders for my units at the same time, I need to erase them to apply the indexer on them?

5(optional xD). If ure very kind, could you pls upload a map that makes two units move to diferent ways continuosly with the indexer?

 

[deathismyfriend]

1) not sure what u mean by replace the hashes ? unless u mean how to use them in the hashtable. u need to use there custom value instead of there Key when saving to a hashtable.

2)the GUI one by bribe uses there custom value. so to use it in an array or hashtable u use there custom value.

3) the best for GUI is the one Bribe made ( i believe)

4) umm not really sure what u mean. if u have old hashtables tho u will have to edit them all to use the indexer but if they are working already and u use key of the unit then u dont need to do this.

5) sry i never use the unit indexer i always index my spells manually.

in my tutorial there is a chapter that can help u with indexing. it is more efficient than hashtables and IMO easier to do.

http://www.hiveworkshop.com/forums/tutorial-submission-283/things-gui-user-should-know-233242/

 

[Nestharus]

Indexers accomplish three things

#1: They can detect whenever a unit is made
#2: They can detect whenever a unit is removed or decays
#3: They assign each unit an index between 1 and 8191. Those ids can be used in arrays, so no hashtables required. They make use of unit user data, so they are faster than GetHandleId too.

The best one for GUI atm is Bribe's I believe. The best one for vJASS is mine.

 

[deathismyfriend]

i thought GetHandleId is faster than setting the custom value of the units. how much faster is setting the custom value ?

i shouldve noted that they can be used with arrays.

 

[Almia]

GetHandleId is quite slow. It gives ids for every handle in the map.The more ids,the more it gets slower.

UnitUserData is fast because only units are indexed.

 

[Nestharus]

That's not the reason why, but ok

 

[deathismyfriend]

ok lol. i just figured that the handles would be very because everything is given a handle when it enters map.
Thats good to know that unit user data is faster tho

edit: ooo whats the exact reason Nes ?

 

[Nestharus]

Remember the handle table? It's a table. This means that looking up handle ids is not O(1). This is the reason why GetHandleId is slower than GetUnitUserData.

 

[Almia]

^ At least my answer is quite near

 

[deathismyfriend]

ooo umm didnt know it was a table or what a table is.

 

[Almia]

Handle Table is just like String Table
They are internal.

 

[Nestharus]

^ At least my answer is quite near

Your answer wasn't even close, lol


And on this

Handle Table is just like String Table

no, lol

 

[deathismyfriend]

not sure what string table is either haha.

so what do u mean by Handle Table ?