Re: [Royale] Collection work

ok On 1/3/18, 3:33 PM, "Alex Harui" wrote: >Peter, > >I'm not convinced you need itemAdding events. And item can be added and >removed without impacting selection. Selection management should be >independent of changes to the data provider, and it is up to selection

Re: [Royale] Collection work

It looks good to me. 2018-01-03 20:39 GMT+01:00 Peter Ent : > Well, that bead only dispatches "dataProvidedChanged" regardless of the > reason. And it does so after the data as changed. We want to know before > the data changes so we can save the selection and then after

Re: [Royale] Collection work

Well, that bead only dispatches "dataProvidedChanged" regardless of the reason. And it does so after the data as changed. We want to know before the data changes so we can save the selection and then after the data changes so it can be restored, if possible. We need something to send out an event

Re: [Royale] Collection work

Hi Peter, What about DataProviderItemsChangeNotifier - It exactly doing what you are saying and what that restoration bead needs. What do you think ? Thanks, Piotr 2018-01-03 18:05 GMT+01:00 Peter Ent : > I've spent this morning wrestling with this. > > Right now when

Re: [Royale] Collection work

I've spent this morning wrestling with this. Right now when a model (eg, ArraySelectionModel, ArrayListSelectionModel) has its dataProvider replaced, it will set the selectedIndex to -1 (and selectedItem to null) if the dataProvider is being set to null; otherwise it leaves the values unchanged

Re: [Royale] Collection work

And this one reason we have beads as a pattern. There is no one right way to preserve selection and selection should not always be preserved for certain kinds of data provider changes. So, create a bead that performs the selection preservation you need and give it a name that makes it clear what

Re: [Royale] Collection work

Peter, You didn't misread, but my thoughts probably didn't far away into problem resolution. That's why I was surprise why I haven't thought about preserving selection. :) Thanks, Piotr 2018-01-02 22:10 GMT+01:00 Peter Ent : > I thought because you mentioned that

Re: [Royale] Collection work

How are you doing that preservation, by simply saving item somewhere before remove/add operation ? I'm not following the part where we you wanted some opinion. Actually in case of refreshing I didn't even thing about saving selection, but it's true that it should happen! It's surprises me that in

Re: [Royale] Collection work

The first task is to determine if a list's selectedIndex or selectedItem should be preserved. For selectedIndex, adding or removing an item will get the same row selected until that row no longer exists. For selectedItem, adding or removing an item will keep the same item selected until that

Re: [Royale] Collection work

Hi Peter, I haven't checked your branch yet, but I just pushed couple of things to the develop which I needed for my examples. Here is the list of beads which we currently have and can be used for List. I think names are self explanatory. DynamicAddItemRendererForArrayListData

Re: [Royale] Collection work

Hi Peter, sound very good. That was something needed to work more near of what Flex is. I hope to come back soon to the project this days, and check that, slider and other things done. Have a great break and thanks for the gifts! :) Carlos 2017-12-19 14:09 GMT+01:00 Peter Ent

Re: [Royale] Collection work

The branch is pushed. It is not in features because I don't want it building and possibly failing. Its just for looking. I'll dispose of the branch once things are integrated. ‹peter On 12/18/17, 5:31 PM, "Piotr Zarzycki" wrote: >Hi Peter, > >It looks pretty

Re: [Royale] Collection work

Hi Peter, It looks pretty exciting! This new stuff may help with some sorting. Push the branch and maybe I will look if not I will definitely do this in the new year. Thank you and wish you all the best! Piotr 2017-12-18 23:24 GMT+01:00 Peter Ent : > Piotr (and anyone

[Royale] Collection work

Piotr (and anyone else interested): Adobe has its winter break next week but I am leaving earlier (tomorrow) and will be back working on the project in January. I have created a temporary branch, CollectionData, with my work in-progress. While this branch is incomplete, you might be interested