Can’t test myself, but try to play with the direction and the match edges.
The change was ‘the ability to reach two stop points at the same time’ (not exactly those words) so try to make sure only one stop point is acting each time and it should work like before.
No, what I mean is to try to set all to only act at the left edge of the screen, (or the right). If you set to both, when you scroll both stop points will stop.
No sense? This way only one stop point is acting each time. With your previous setup two stop points were acting simultaneously. And it seems LL don’t like it very much (I think it is a bug Pierre Hébert)
Not really a bug, but confusing maybe. The change was that when several stop points are matching, LL evaluates all of them. In some use cases two or more stop points at the same location and the same direction will conflict or stop scroll more than one time.
D5 Creation
< ![CDATA[
Can’t test myself, but try to play with the direction and the match edges.
The change was ‘the ability to reach two stop points at the same time’ (not exactly those words) so try to make sure only one stop point is acting each time and it should work like before.
]]>
< ![CDATA[
TrianguloY does it mean i need 2 stoppoints instead of one like before? one for > another one for < instead of one <>?
]]>
< ![CDATA[
No, what I mean is to try to set all to only act at the left edge of the screen, (or the right). If you set to both, when you scroll both stop points will stop.
The direction should work with both.
]]>
< ![CDATA[
sorry, but i didn’t understand ;-(
it works with 2 stoppoints instead of one.
and each has to be configured with this edge-stuff…
i can’t get it to work with only one.
grrrr, much more configration as before;-((
need a copy-style for stop-points !!!!!!
]]>
< ![CDATA[
It seems to work for me.
Direction: left to right and right to left
Match edge: left only
]]>
< ![CDATA[
TrianguloY you’re right. .this works too, but makes no sense in my option.
]]>
< ![CDATA[
No sense? This way only one stop point is acting each time. With your previous setup two stop points were acting simultaneously. And it seems LL don’t like it very much (I think it is a bug Pierre Hébert)
]]>
< ![CDATA[
TrianguloY i mean it is confusi g. 🙂
]]>
< ![CDATA[
Not really a bug, but confusing maybe. The change was that when several stop points are matching, LL evaluates all of them. In some use cases two or more stop points at the same location and the same direction will conflict or stop scroll more than one time.
]]>