Asynchronous loading texture

[VisualSJ]

CCEventHelper

• removeEventListener must be incoming listener
• add removeEventTarget

CCSprite

• When setting the texture, you need to clear the callback

Menu/Scale9Sprite/Button asynchronous loading texture

[pandamicro]

No need to do this, you are checking it in the next if

[VisualSJ]

Each interface for replace texture need to judge the state of loaded
In the case of load===false, Increase the waiting listener.

The listener will call the function again after the completion of loading.
Before is the direct execution function, then update data after loading successfully, update logic is too confusing...

[VisualSJ]

@pandamicro

[VisualSJ]

Uniform update after successful loading

[1scaR1]

Something strange with sprite positions if some non-trivial transformations are applied to them(for example with composition from parent's transform)

[pandamicro]

for example with composition from parent's transform)

I don't understand, what do you mean by compositing parent transform ?

[1scaR1]

I found example when anchor point is ignored:

        cc.spriteFrameCache.addSpriteFrames(res.some_plist);

        this.setContentSize(cc.director.getWinSize());

        var firstLayer = new cc.LayerColor(cc.color.RED);
        firstLayer.setContentSize(600,600);
        firstLayer.setScaleY(0.5);

        var secondLayer = new cc.LayerColor(cc.color.GREEN);
        secondLayer.setRotation(45);
        secondLayer.setContentSize(600,600);

        var sprite1 = new cc.Sprite(cc.spriteFrameCache.getSpriteFrame('some_frame_name.png'));

        secondLayer.addChild(sprite1);
        firstLayer.addChild(secondLayer);
        firstLayer.setPosition(300,50);

        this.addChild(firstLayer);

In this example center of sprite1 must be at left-center corner of green layer. But it is in green layer(like anchor point is ignored).
It only works with sprite frames, not directly loaded texture.

[pandamicro]

@1scaR1 Sorry just see your comment, I have asked @VisualSJ to take a look

[VisualSJ]

Thanks @1scaR1

Before the default value is set in the initTexture...

The default value should be set within the ctor...