On Wed, Sep 3, 2008 at 6:19 PM, Kao Cardoso Felix <[EMAIL PROTECTED]> wrote: > > This is okay until I try to remove a node by name. An exception is > raised because a str object obviously doesn't have a set_batch method. > As removing by name is supported on the cocosnode version of the > method it should be here too, I think.
fixed. added test_batch2.py for this. rev746. > there is some nice design pattern that could be used here? not that i know of. ideas? > The other issue I've observed is that when one adds a named child to a > node and then remove it by reference, the name doesn't get removed. > This way, when I try to add another children with the same name I get > a "Name already exists". From my point of view, as names are unique, > when an named instance is removed by reference, the associated name > should be removed as well. we talked about this issue, and decided that if you add by name, you should remove by name. this is beucase we didnt want to be checking the name list on every remove (we would need an inverted index also). i think that this decision can be reversed. how strongly do you feel about this? lucio. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cocos-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
