A little confusing at the end. You're probably saying that the component that contains the common controls, between the two ViewStack child Canvases, isn't persisting it's state; when you switch back and forth.
If you have controls that are common to both views, perhaps using ViewStates would work better in this case. The way that its probably setup currently, is that you have a seperate instance of the component in each of the Canvases. To maintain state for your common component, just add/remove the other stuff using ViewStates. Or, you can take the component out of the ViewStack and layer it on top. -TH --- In [email protected], "pvgirishkumar11" <[EMAIL PROTECTED]> wrote: > > Hello friends, > > I run into a problem with viewstack and accesing child components. > Here is the problem, I have a viewstack which contains 2 canvases both > contains front and back images of a mobile. And I have an Component > which contains set of controls which i use on both canvas... > > The problem is when i made any changes to first canvas(viewstack -child > one)and then i move back to second one and edit it. when again i came > to access the first one its not working and its doesnt change the last > used control on that canvas.. > > pls get me out of this... > > Cheers > GIRISH.. >
