Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
Contributor
rrenna
Posts: 13
Registered: ‎05-02-2012
My Device: Playbook
My Carrier: Rogers
Accepted Solution

Cascades, subclass of AbstractPane

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.

Please use plain text.
BlackBerry Development Advisor (Retired)
gperry
Posts: 138
Registered: ‎05-11-2012
My Device: Developer
My Carrier: Developer

Re: Cascades, subclass of AbstractPane

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.

Please use plain text.
BlackBerry Development Advisor (Retired)
gperry
Posts: 138
Registered: ‎05-11-2012
My Device: Developer
My Carrier: Developer

Re: Cascades, subclass of AbstractPane

Was this information sufficient to mark this thread as solved?

 

Graham

Please use plain text.