The latest build that I pushed this morning seems to behave much better, even 
on my old phone where I could "kind of" reproduce what you describe.

Did you have a chance to try it?

/D

On April 14, 2018 10:11:31 PM PDT, Linus Torvalds 
<torva...@linux-foundation.org> wrote:
>On Sat, Apr 14, 2018, 21:08 Linus Torvalds
><torva...@linux-foundation.org>
>wrote:
>
>>
>> It's very clear, and happens both with all trips collapsed and with
>one or
>> more trips exposed. I can scroll down once, but when I try to scroll
>> further, at first nothing happens at all, then it resets to an
>earlier
>> state (maybe back to the top) and then it scrolls down some more.
>>
>
>Ok, so there is a pattern to the oddity.
>
>I tried to move my finger very slowly and keep track of where my finger
>was
>and which entry I was touching.
>
>I may not be great at explaining the behavior I see, but imagine that
>you
>have all trips collapsed, and the first scroll event is you touching a
>trip
>right in the middle of the screen, and slowly moving your finger up.
>Everything works fine.
>
>It at least *almost* fine. I think there is an off-by-one error, where
>when
>I put my finger down tp before I move it, the dive list jumps by one
>entry.
>So there is a small jerk event happening even there, but it's almost
>unnoticeable. The scrolling itself is fairly smooth once I start moving
>my
>finger.
>
>Then, release the finger, and start the next scroll event lower down
>(say,
>three quarters of to the bottom), and moved your finger up to scroll.
>
>During that second scroll event, *nothing* happens in the screen for me
>at
>first, until my finger hits the point where I started the *first*
>scroll
>(so I moved my finger from 3/4 down the screen up to the halfway point
>without anything moving at all). But when I hit that point where I
>started
>my previous scroll, the dive log screen resets to where it was the
>*last*
>scroll event, and then starts scrolling with my finger again.
>
>So I never and up making any actual progress, and it feels really jerky
>because part of the time the screen doesn't react to the finger at all,
>and
>then when you pass a certain point it jumps and starts reacting again,
>just
>at the wrong place.
>
>So there seems to be some "screen offset" thing going on, with some
>history.
>
>Except *occasionally* the second scroll event works fine. So I can make
>some progress every once in a while. I didn't figure out the pattern
>for
>that, though.
>
>       Linus
>
>>

-- 
from my phone.
_______________________________________________
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to