I think Ansca should think about renaming “insert()” on display objects to something else like “move()” to reflect what is done and make it easier to understand what happens for new users!
See this post:
http://developer.anscamobile.com/forum/2010/07/19/preferences-screen-sample-code#comment-4118 [import]uid: 6928 topic_id: 1478 reply_id: 301478[/import]
I don’t think so. You insert it at a certain position inside a group. Or at the end. The term “Move” only covers something existing.
If you want to nickpick, then let someone only add into a group with “INSERT” and reposition it ith a “MOVE”
I say leave it like it is if yoiu don’t want to seperate this functionality. [import]uid: 5712 topic_id: 1478 reply_id: 4123[/import]
Everything is added to the stage on creation… So the object exists … Hence you move it somewhere else till you “remove” it… After that… You insert it … For the first time…
Insert removes it from where it origins … And moves it into another group … It has only one position in the hierarchy.
I agree that “move” is also not the best term … As the method is the one of the group not the one of the object. “attach” and “detach” … Wahtever.
Sure you can say I insert it into some group … But … Look at tables and how insert works there! When I insert something twice … I expect it to be there twice!
Also I do not expect something to get removed somewhere else if I insert it somewhere.
I do not nitpick but tell about what I read on the forum that multiple users had problems with … And I think that is because insert is associated with it’s functionality for tables. Which is different… [import]uid: 6928 topic_id: 1478 reply_id: 4125[/import]