I think I was wrong. It looks like our code which is causing this. We’re not 
actually changing the DataProvider. We’re changing the source.

Sorry for the noise...

> On Jun 22, 2020, at 10:32 AM, Alex Harui <[email protected]> wrote:
> 
> Do you have an older version that works?  What kinds of data provider 
> changes?  I'd check the DOM and see if the renderer parent is being given a 
> size.  It could be the "scroll to top" was accidental because all renderers 
> were removed and the parent element could shrink.
> 
> HTH,
> -Alex
> 
> On 6/21/20, 11:45 PM, "Harbs" <[email protected]> wrote:
> 
>    Basic. The item renderers are using Spectrum.
> 
>        <js:MultiSelectionList id="imageGrid" 
> itemRenderer="com.printui.view.renderers.ImageTile" width="100%" 
> style="padding-right:10px;padding-left:10px;border-width:0;">
>          <js:beads>
>            <js:TileLayout id="gridLayout"/>
>            <js:CollectionChangeUpdateForArrayListData/>
>            <js:MultiSelectionCollectionViewModel/>
>            <js:DynamicRemoveAllItemRendererForArrayListData/>
>            <js:DataItemRendererFactoryForCollectionView/>
>          </js:beads>
>        </js:MultiSelectionList>
>        <js:MultiSelectionTree id="imageTree" 
> itemRenderer="com.printui.view.renderers.ImageRow"  width="100%" 
> style="border: none;">
>        </js:MultiSelectionTree>
> 
> 
>> On Jun 22, 2020, at 9:32 AM, Alex Harui <[email protected]> wrote:
>> 
>> What I'm asking is what beads you are using in your app for the TileLayout.  
>> What Layout bead are you using?  Are there ItemRenderers and how are they 
>> generated?  I don't even know if you are using Jewel or Basic or something 
>> else in your app.
>> 
>> On 6/21/20, 10:52 PM, "Harbs" <[email protected]> wrote:
>> 
>>   I’m not sure. I need to debug to figure out where the issue is.
>> 
>>   I was hoping someone might be aware of a change that might effect this.
>> 
>>> On Jun 22, 2020, at 8:26 AM, Alex Harui <[email protected]> wrote:
>>> 
>>> What beads are involved?  Does it behave the way you expect in the 0.9.7 
>>> release?  Maybe you can find the code that resets scroll position in that 
>>> version so you know what code might have gone missing.
>>> 
>>> -Alex
>>> 
>>> On 6/21/20, 10:19 PM, "Harbs" <[email protected]> wrote:
>>> 
>>>  I’d like to get this resolved before I start on the release.
>>> 
>>>> On Jun 21, 2020, at 10:55 PM, Harbs <[email protected]> wrote:
>>>> 
>>>> I just noticed a change in behavior, but I don’t know where it was 
>>>> introduced.
>>>> 
>>>> I have a tile layout where I change the data provider. When that happened, 
>>>> it used to scroll back to the top. (same applies to a tree layout)
>>>> 
>>>> Currently, the scroll position remains where it was.
>>>> 
>>>> Any clue why/how that changed?
>>>> 
>>>> Harbs
>>> 
>>> 
>>> 
>> 
>> 
>> 
> 
> 
> 

Reply via email to