Hi, simple yet stupid problem - I have a view. And the view handles commands. I want to close that view as a responce to a command. I can not do a RemoveView() because it will cause a panic as the object I call RemoveView from is not valid any more. Any ideas?
I just want. My app has views coming and going. It is the nature of it. Yes, I can remove it from tab and just not to display it any more but I loose memory this way.
you don't need to worry about view because AppUi is taking care of it, when u do AddViewL that time u have transfered the Owenership of ur view to AppUi. U just't can't delete it, otherwise it will panic. Anyway u also no need to bother about memory, because view does not take much memory, what all it contains is a container and as the view get deactivate, the container should be deleted, that's what the symbian's view architecture.
I don't agree with this at all. Let's say I have a editor which is capable of opening several text files to edit. I don't see it reasonable to: 1) keep them open all the time with all this richtext and stuff allocated 2) to create/delete them all the time I take a peek into other text document with DoActivate/DoDeactivate
Forum posts: 122
Forum posts: 47
I just want. My app has views coming and going. It is the nature of it. Yes, I can remove it from tab and just not to display it any more but I loose memory this way.
Ahti.
Forum posts: 188
Anyway u also no need to bother about memory, because view does not take much memory, what all it contains is a container and as the view get deactivate, the container should be deleted, that's what the symbian's view architecture.
BR
Chetan
----
Chetan Kulshrestha
Forum posts: 47
I don't agree with this at all.
Let's say I have a editor which is capable of opening several text files to edit. I don't see it reasonable to:
1) keep them open all the time with all this richtext and stuff allocated
2) to create/delete them all the time I take a peek into other text document with DoActivate/DoDeactivate
Don't you agree?
Ahti.