05-10-2012 02:24 PM
Is subclassing AbstracePane for the purpose of creating custom screens in cascades possible? If so, is it encouraged? I'm trying to wrap my head around Custom Controls, and where to section off logic for seperate screen types.
For instance, if I list FOOs, and I want a CreateFOO screen. Should I push a Page, with a custom CreateFOOView custom control. Or should I have a subclass of AbstractPane, and push that onto the navigation stack.
Hope someone can clarify the correct way of approaching this.
Solved! Go to Solution.
05-16-2012 02:08 PM
AbstractPane is not really intended for that level of sub-classing - the supplied concrete subclasses such as page would be better suited to your purposes.
In the Sample App Stamp collector; ContentPage.xml is a good example of a page that is not the root page.