FlxNapeSprite: add support for compound bodies

[thegoodideaco]

If the body is part of a compound, then it's space cannot be changed, instead must be added/removed from the compound bodies list

[Gama11]

Seems the /** here was duplicated?

[thegoodideaco]

ahh crap, fixing

[Gama11]

Any nape demo or code I could use to test this with?

[thegoodideaco]

I can make a quick example if you like.

[Gama11]

Are you sure it shouldn't look like this?

if (body != null)
{
    if (body.compound == null)
        body.space = FlxNapeSpace.space;
    else
        body.compound.bodies.add(body);
}

Right now it would add null to compound.bodies.

[thegoodideaco]

@Gama11 : https://github.com/thegoodideaco/FlxNapeSpriteTest for an example.

[Gama11]

Thanks!

set_physicsEnabled() can still cause a crash. Should probably move the logic for adding a body / removing a body into separate methods to avoid redundancy and to be usable from there.

[Gama11]

Any update? :)

[thegoodideaco]

Should be ready to rock

[Gama11]

This code section looks like an exact copy of the one in revive().

[Gama11]

The most recent commit doesn't seem to have any impact on the set_physEnabled crash:

Error: Cannot set the space of a Body belonging to a Compound, only the root Compound space can be set

(see https://github.com/Gama11/FlxNapeSpriteTest)

[thegoodideaco]

This is odd, let me look

[thegoodideaco]

i think we need to add an additional property to store any compound it might be apart of. If we disable physics, we have to remove it from the compound instead of from space. We need something to reference if they enable physics again

[Gama11]

Hm... this is getting pretty complex. I should finally get around to setting up unit tests for flixel-addons so we can test all these different cases..

[thegoodideaco]

I agree

[Gama11]

Closing this for now since there's still some unresolved issues, I created an issue as a reminder: #321