|
| 05 Feb 2013 09:07 PM |
| IT'S INEFFICIENT, WASTEFUL, AND DEPRECATED |
|
|
| Report Abuse |
|
|
|
| 05 Feb 2013 09:08 PM |
(Oops I forgot to mention, using :Destroy() is the new method, it actually locks the parent and removes all the properties. Same thing with all it's children)
crescendoflip |
|
|
| Report Abuse |
|
|
|
| 05 Feb 2013 09:10 PM |
but what if you wanna set somethings parent to nil and retrieve it later? I rather put game.Workspace.Part:remove() than game.Workspace.Part.Parent = nil.
~ Moo logic = logical logic ~ |
|
|
| Report Abuse |
|
|
DrHaximus
|
  |
| Joined: 22 Nov 2011 |
| Total Posts: 8410 |
|
|
| 05 Feb 2013 09:10 PM |
@18
and id rather use non-depreciated methods |
|
|
| Report Abuse |
|
|
|
| 05 Feb 2013 09:11 PM |
cOLD mOLD
Why you make useless spam post?!? |
|
|
| Report Abuse |
|
|
|
| 05 Feb 2013 09:11 PM |
| And what if remove is just as efficient if not more than destroy? Destroy locks the parent and disconnects all events. |
|
|
| Report Abuse |
|
|
|
| 05 Feb 2013 09:12 PM |
| Destroy disconnects everything, removes the properties, and locks the parent. Remove is the exact same is object.Parent = nil. |
|
|
| Report Abuse |
|
|
|
| 05 Feb 2013 09:14 PM |
| No, the properties are not removed. |
|
|
| Report Abuse |
|
|
| |
|
|
| 05 Feb 2013 09:17 PM |
Remove has only one up side(that i know of) and its shorter than saying .Parent = nil (by 4 letters, which can make a difference)
~ Moo logic = logical logic ~ |
|
|
| Report Abuse |
|
|
miz656
|
  |
| Joined: 19 Jul 2010 |
| Total Posts: 15336 |
|
|
| 05 Feb 2013 10:07 PM |
Fine. I won't use Remove(). I'll just parent its object to nil.
Score! |
|
|
| Report Abuse |
|
|
|
| 05 Feb 2013 10:11 PM |
Fine I won't use Remove(). Ill use remove().
~ Moo logic = logical logic ~ |
|
|
| Report Abuse |
|
|
miz656
|
  |
| Joined: 19 Jul 2010 |
| Total Posts: 15336 |
|
| |
|
| |
|
Merely
|
  |
| Joined: 07 Dec 2010 |
| Total Posts: 17266 |
|
|
| 06 Feb 2013 01:50 AM |
| Benchmark before you optimize. Unless you're dealing with adding/removing hundreds or thousands of bricks, it probably doesn't make a huge difference. The garbage collector gets it eventually. |
|
|
| Report Abuse |
|
|
|
| 06 Feb 2013 02:09 AM |
'and id rather use non-depreciated methods'
Depreciated? Are you saying the Remove method is no appreciated and you don't like that?
Oh yeah, it's deprecated too. |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 06 Feb 2013 02:36 AM |
| Dis was such an useless thread.... Not even mentioning how cOLD this is. |
|
|
| Report Abuse |
|
|
|
| 06 Feb 2013 02:38 AM |
| if you arent going to talk about the topic then dont post zars |
|
|
| Report Abuse |
|
|
LocalChum
|
  |
| Joined: 04 Mar 2011 |
| Total Posts: 6906 |
|
|
| 06 Feb 2013 02:49 AM |
fine i'll .Parent = nil
it does the same thing |
|
|
| Report Abuse |
|
|
| |
|
Seranok
|
  |
| Joined: 12 Dec 2009 |
| Total Posts: 11083 |
|
|
| 06 Feb 2013 03:25 AM |
No one in this thread seems to realize that the Remove method also orphans all descendants. It's not equivalent to .Parent = nil.
If you want to use the object no more, use Destroy If you want to store it outside the DataModel, use .Parent = nil If you want to do what Remove does: instance.Parent = nil instance:ClearAllChildren() |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
| |
|
|
| 06 Feb 2013 05:21 AM |
| no it isnt dont try to change my mind |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 06 Feb 2013 05:27 AM |
| I don't have to. I am your mind. |
|
|
| Report Abuse |
|
|
|
| 06 Feb 2013 05:29 AM |
| no tenal is my mind body and soul |
|
|
| Report Abuse |
|
|