Why are g_initializePlugin() and g_deinitializePlugin() called multiple times?

bowerandy

I'm using the IOS player and I see the following with one of my plugins:

on launch of player:
init
deinit

on launch of app:
deinit
init
deinit
init

on shutdown of app
deinit
init

Seems a bit over-keen to me.

Best regards

ar2rsawseen

By IOS player you mean Gideros player with integrated plugin?

bowerandy

Yes, I mean the player running on an actual IOS device.

Also notice the shutdown sequence - it seems strange that it ends with an init().

atilim

g_initializePlugin() is called after creating the lua_State and g_deinitializePlugin() is called before closing lua_State. But you're right. Let me optimize it.

bowerandy

@atilim, having now seen my post about the Wax plug-in perhaps you can now see the reason for this question about initialization/deinitialization.

I'm using these hooks to start and stop the Wax system in my BhWax plugin. I'm not quite sure what overhead there in in doing this but, obviously, having to go round the start/stop loop three times before an app gets of the ground can't really be a good thing.

It would be good if you could fix this in the next version of the system or perhaps you have an alternative suggestion as to where I can place the wax_setup/wax_end calls?

Best regards