Databases
StackOverflow2013
Postsdbo
POSpriteKit SKAction doesn't work after removing and readding a node
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpriteKit SKAction doesn't work after removing and readding a node
    primarykey
    data
    text
    <p>Been banging my head against this for a day now, and I really have no idea what's going on.</p> <p>I have a very simple setup: an SKNode (let's call it base) which contains another SKNode (sub-base), as well as several SKShapeNode objects. At some time, I move one of the SKShapeNode objects (using removeFromParent) from the base node to the sub-base node. Then I apply an SKAction, which moves the node to some arbitrary position.</p> <p>Except, that SKAction does not work when the SKShapeNode has been removed and added to the sub-base object. If I remove it from the sub-base, and put it back in the base, SKActions once again work. </p> <p>I am completely stumped. Is there some property that gets set on a node when it's added to another node, which isn't getting properly reset when I remove it...? I can't imagine this is something that should be happening. </p> <p>Any ideas would be so very welcome.</p> <p>Update:</p> <p>Here's some code that I can produce it with. This function is inside a subclass of SKNode. The class adds a bunch of SKShapeNodes, and it also has this other SKNode called testNode, so, without further ado:</p> <pre><code>-(void) removeThenAdd { [someNode removeFromParent]; [self.testNode addChild:someNode]; SKAction* action = [SKAction moveTo:CGPointMake(200, 200) duration:1]; SKNode* thatSameNodeJustAdded = [self.testNode.children objectAtIndex:0]; [thatSameNodeJustAdded runAction:action]; } </code></pre> <p>Another update!</p> <p>I just found that, if I add an SKAction to the node whilst it is sitting inside the testNode, then after that remove it from the testNode and add it back to its original parent, the action is then activated. Like, what am I missing here? This must be some kind of designed behaviour I'm just not using right..</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdebu
    1. USdebu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COShow the transfer code and the actions you run. I can imagine that the move actions are initialized with the node's original position (and parent coordinate space) and don't update their target destination when you "reparent" the node.
      singulars
      1. POSpriteKit SKAction doesn't work after removing and readding a node
      1. USLearnCocos2D
    2. COI'm recreating the action, in some cases, much later after the node was reparented, so I guess it can't be that? Anyway, I put some code up.
      singulars
      1. POSpriteKit SKAction doesn't work after removing and readding a node
      1. USdebu
    3. COWhen you say "it doesn't work", you need to be more specific. Do you get an error ? It doesn't move how you expect ? If so, tell us what exactly it does, so we can utilize that information. It sounds like maybe this is possibly about you using MoveTo and not expecting the SKNode to work differently because it now has a new coordinate space. 200,200 with the original parent, is likely not the same global location as with the new parent. Be more specific if you can.
      singulars
      1. POSpriteKit SKAction doesn't work after removing and readding a node
      1. USprototypical
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload