02-04-2014 02:40 PM
And in 10.2.1 the Quick Settings has an option to Rearrange.
Would be nice if BB would share.
02-04-2014 03:04 PM
Well spotted, I missed that.
However it's no surprise that they would wish to trial something internally before releasing it to all developers.
Looking forward to this now and I was wondering how they would implement it, now we know.
02-05-2014 05:33 AM
Rearranging of the model data is not the problem this can be done with all the data models.
The problem was coming up with a consistant approach to rearranging lists that would be okay with users.
I held off doing it myself in the hope that the BlackBerry way would be implemented soon, that was over a year ago now.
Doing what Lazy Lists has done would be fairly easy but it goes against some of the BlackBerry guidelines, frankly I'm surprised it got a Build For BlackBerry certification. Actually I'm *not* surprised, we all know what a mess was made of entry in to that program.
Now it's been pointed out that this list rearrangement exists in Settings, if you look, it's in a few other places as well such as the Hub settings.
The BlackBerry approach fits in to the current UIX maintaining long-hold integrity as a context menu invoker as Lazy Lists does not.
I look forward to finally getting to implement it in my app on the next NDK iteration. Fingers crossed!
05-28-2014 03:13 PM
I know I am resurrecting a thread but it seemed like a good place to ask:
As of 10.3 SDK Cascades has a RearrangeHandler in ListView and it works quite well and it's easy to implement.
However I have a problem that it works only in the opposite direction of the list orientation in StackListLayout... ?
I'm using the move function on ArrayDataModel to actually move list items.
Any examples or docs or suggestions how to properly use RearrangeHandler?
07-28-2014 04:28 AM
08-01-2014 12:24 PM
I already have and I am aware of it. It's classified as a major bug which it is. However it's like that for months now. Really, there must be some solution that can be used to fix it.
Perhaps a change of model type?
08-01-2014 04:58 PM
08-12-2014 02:50 AM
Bump up with this.
Also, a little secret bird beta tester informed me that this hasn't been fixed yet on the latest running build on Passport.
To my knowledge all that has to be done is disengage parent scrolling upon onMoveStarted. Perhaps there is more to it than I can see in a closed source Cascades control.