| 05-24-2004, 12:17 AM | #1 |
Basically I want the effect of RemoveUnit(myUnit) without the leak. Do you ExplodeUnit(myUnit) then RemoveUnit(myUnit) that Unit? Is it ExplodeUnit(myUnit) then ShowUnitHide(myUnit,true) ? What is the general concensus on the safe way to make a unit appear to completely disappear without leaking? |
| 05-24-2004, 02:55 AM | #2 |
Would moving a unit, making it untargetable, and then killing it work? |
| 05-24-2004, 09:20 AM | #3 | |
Quote:
Removing the unit and setting the variable to null (No Unit in GUI) should work well enough. |
| 05-24-2004, 01:53 PM | #4 |
I'm still oblivioux to where this rumor of "Removing Units" leaking - came up o_O. There is no truth to that rumor, it's...bs. And i'm interested in seeing where (why) it appeared. Anyways, there is only one rare occasion where it can be buggy to instantly Remove it, and then it's better to first kill it, then remove it. So I tend to do that all the time when needing to kill a unit. I have my own function that I use: function DestroyUnit takes unit u returns nothing call KillUnit(u) call RemoveUnit(u) endfunction Anyways. ~Cubasis |
| 05-24-2004, 02:41 PM | #5 | |
Quote:
|
| 05-24-2004, 03:19 PM | #6 |
eh? .... Not really knowing what you mean, but everything that exists in GUI exists in JASS .... becouse GUI is just a user interface for JASS. That is, everything you do in GUI gets converted to JASS when you save. ~Cubasis |
| 05-24-2004, 11:03 PM | #7 |
Actually I think that the rumor of removing units causing leaks started a while ago before locations and groups where identified as leakable (before we understood anything about leaks actually) Probly the tests that tried to probe that Removing Units leaked had leaking locations |
