Hi, i've used Starling.handleLostContext = true; before create Starling instance.
But when i change device orientation on android I get Error :3694
I dispose textures myself, becouse when orientation is changed I need to create them in different size.
Do you have a callstack? Who throws that error?
I must wait till tomorrow becouse don't have android device now. But it was from Starling class.
I'll put callstack tomorrow.
Hi, i have callstack:
Error: Error #3694: The object was disposed by an earlier call of dispose() on it.
at flash.display3D::Context3D/configureBackBuffer()
at starling.core::Starling/updateViewPort()[/Users/redge/Development/starling/starling/src/starling/core/Starling.as:257]
at starling.core::Starling/set viewPort()[/Users/redge/Development/starling/starling/src/starling/core/Starling.as:537
Daniel can You look at the callstack and help me? 
I guess this is happening with Starling 1.1 (latest official release), right? Could you try to use the latest head revision from GitHub? If the error pops up there, too, please post the call stack again. (To have the right line numbers.)
Thanks! =)
Sorry for late answer:
Error: Error #3694: The object was disposed by an earlier call of dispose() on it. at flash.display3D::Context3D/createTexture() at starling.textures::Texture$/fromBitmapData()[E:\work\FlipbookMobilePlayer\src\starling\textures\Texture.as:134]
Right now I have workaround. I don't upload new textures until context is recreated.
Its a simple problem you are probably trying to create/upload a texture after device loss but before it was recreated.
I handled this in Genome2D as it is surprisingly quite often when people create textures even when the application is in the background or on some kind of event/timer where you can't know if there is device loss at the moment or not. So this must be handled by Starling at core to postpone initialization/upload of context texture till its possible.
Or you need to manage it at your side to avoid this when there is device loss which can be tricky.
Thanks for the information, sHTiF. Ah, that damn context loss ... why can only Apple handle this on the driver side?! *sigh* I'll look into it.
You must log in to post.
