Crashes removing display objects
Posted on Sun, 2010-03-07 07:13
I can't totally confirm this, but I've seen a few crashes in instances where I removed an object from the display hierarchy but kept a variable referencing said object.
Replies
Posted on Mon, 2010-03-08 12:16
#2
dwallin33
do you have code you can send us to see the bug you are seeing? info@asncamobile.com
thanks
carlos
Posted on Thu, 2010-04-29 19:17
#3
(Logged as bug #129)
Posted on Thu, 2010-05-06 13:00
#4
we can't reproduce. is there some code you guys can send to us that reproduces this on your drop?
please send to support@anscamobile.com
carlos
dwallin33,
I don't know if it could help you, but I was having trouble with newGroup treatment in SDK 1.1 that was running on SDK 1.0.
I was using a menu=display.newGroup() to keep my menu buttons organized. Then I used a transition.to(menu, delay...) Everything was well except, when I removed by calling a function like this:
function freeMenu()
--if disableMenuListener() then
for i=menu.numChildren,1,-1 do
local child = menu[i]
child.isVisible=false
menu:remove( child )
child=nil
end
--end
return true
end
which is expected to remove only childs under menu Group. The things is after removal, menu group goes to indeterminate state. So, when I called again my buildMenu() function, which only makes menu:insert(startButton) etc, it reports an error producing a stack traceback, due nil value related to menu. This function was well running on SDK 1.0, but for some reason I have to change it to work in SDK 1.1
I don't know if it can help you or not, but I think it can be useful any way.
Flavio.