Closed yuraj11 closed 4 years ago
We can disconnect the signal before assigning the new skin. Alternatively, we can set the skin, not do the signal connection when a skin was already there and trigger the signal in the c code itself.
@rayxuln What is the purpose of the signal? The skin will not change by itself but has to be assigned manually, meaning the programmer can run the signal itself. Looking over the code, I think we can remove the signal completely since setting the skin will also run update_runtime_skin.
It's for notifying the SpineSprite to change the skin when the user changed the skin names in the packed skin resources in the editor.
Don't know why this error happened, but it's not fetal.
I'll fix it later.
You just need to disconnect signal from the old skin if it’s there.
Thomas
On Jul 20, 2020, at 8:15 PM, Rayxuln notifications@github.com wrote:
It's for noticing the SpineSprite to change the skin when the user changed the skin names in the packed skin resources in the editor.
Don't know why this error happened, but it's not fetal.
I'll fix it later.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
If that signal is needed, then my pr did it wrong by removing it entirely.
Thomas
On Jul 20, 2020, at 8:15 PM, Rayxuln notifications@github.com wrote:
It's for noticing the SpineSprite to change the skin when the user changed the skin names in the packed skin resources in the editor.
Don't know why this error happened, but it's not fetal.
I'll fix it later.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Thanks. Fixed!
Calling this when skin skin resource is already set:
causes this issue in logs: