Hi, I have put together a small example that shows the current behavior of a Jewel List when row changes [1]. It's simple, the scroll movement does not depend on the selected row. If we move to an "index" outside the limits of the visible area we must call myList.scrollToIndex (myNewIndex) to force its display.
[1] https://drive.google.com/file/d/17JYeqg5A3o5ub4MdD_icRmiQvuGab245/view?usp=sharing In my view, these two behaviors go together at the presentation level, in the view, and I think it is impractical for the developer to have to remember that the command "position yourself at index x" does not include "and show it to me" 😝 Why not link them or at least give the possibility to configure it and choose whether to do it or not? I see two options: 1st) Call scrollToIndex at the end of the selectionChangeHandler function. (We fix the behavior) 2nd) Create a bead that adds this functionality whenever you want. In my case, I have extended the ListView bead and override the selectionChangeHandler function (first choice): override protected function selectionChangeHandler(event:Event):void { super.selectionChangeHandler(event); scrollToIndex(lastSelectedIndex); } This solution works for me, but thinking about being able to incorporate this possibility in the SDK, I don't know if the second option would be more correct, creating a different bead that can be added or not, depending on the situation. Would the second option be more correct? ? I can think of a third option, which I think is the most versatile: Create the new bead and also create a property in the List "autoscroll = true / false", so that if autoscroll = true we would load the automatically created bead. As you see? I appreciate any comments. Thank you. Hiedra. -----Mensaje original----- De: Andrew Wetmore <[email protected]> Enviado el: martes, 6 de octubre de 2020 1:48 Para: Apache Royale Development <[email protected]> Asunto: Re: Jewel List - selectionChange It seems to make good sense. On Mon., Oct. 5, 2020, 8:46 p.m. Carlos Rovira, <[email protected]<mailto:[email protected]>> wrote: > I guess you mean a programmatic selection? not a user click or touch right? > (since for the later I guess we already have it visible to make the > selection, isn't it?). > > Don't see any problem with doing that, if nobody states something > against it we can implement it. > > Thanks > > El mar., 6 oct. 2020 a las 1:31, Maria Jose Esteve > (<[email protected]<mailto:[email protected]>>) > escribió: > > > Hello, I wanted to ask a question ... I'm sure there is an > > explanation that I can't see ... > > Why is it that when we select a row in a List control, a > > scrollToIndex is not performed to make it visible? > > Is there a situation where I insert a List control and don't want to > > see the item I have selected? What am I missing? > > > > Thx. > > Hiedra > > > > > -- > Carlos Rovira > http://about.me/carlosrovira >
