23 Feb 2013 10:31 AM #1
Any chance the items property could be promoted as a public property for MixedCollection? I've seen it used quite a lot in example code on the forums, but I'm always nervy about using stuff that's not promoted as a public element in the API (have seen some go the way of the dinosaur before).
*I'd put in a feature request in the feature request forum, but it looks like my support is lapsed and our procurement is dragging their feet on renewing me.
23 Feb 2013 1:04 PM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
This for Ext JS 4 or ST 2?Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
23 Feb 2013 1:07 PM #3
Oh, sorry. Actually, both. It looks like both set up me.items =  in the AbstractMixedCollection constructor.
Would be helpful to have that items array accessible as a public property in both ST and ExtJS both.
4 Mar 2013 12:30 PM #4
items has existed since 2.0.
Unless there is a *huge* rearchitecture, i wouldn't worry about it going away.
4 Mar 2013 12:34 PM #5
Cool. Fair enough. Consider my appeal withdrawn.