The poll is not yet ended, but it seems that the outcome is near certain ;-)
The poll is not yet ended, but it seems that the outcome is near certain 😉
While I was thinking at it, I came to the conclusion that the option “Use auto scroll stops” is rather useless and that it could be removed. I’d like to know however if someone is actually using it or if it can be removed safely ?
]]>« aOS (Previous Post)
(Next Post) If i want to create an APK from my Desktop it is possible to add zw-files and icons or other stuff? »
D5 Creation
< ![CDATA[
Its handy in the app drawr, not so much on the desktop. Perhaps make it a multiple choice toggle?
I think I would prefer to place a horizontal or vertical infinite loop stop manually. But im sure everyone wants to to it a diffrent way.
Of course I dont know if I would use them. As for most layouts I think of where I want infinte scrolling I find I can achieve it with multiple pages as well. And those already infinite scroll.
]]>
< ![CDATA[
I’ve been searching for two days the way to configure my screen with hideable side bars, and I thought that the stop scrolling points were the solution to do it. Thanks to other members of this community, I’ve learnt another way to do it (fit desktop to items), so I think I don’t need stop scrolling points any more. Anyway, I don’t know if others would find them useful for other configuration.
Thanks, Pierre, for your amazing work.
]]>
< ![CDATA[
In the places I currently use the auto scroll stops feature I could easily use scrolling stop points instead. Removing the feature would be OK with me…
]]>
< ![CDATA[
Ok I will keep it then 🙂
What is annoying is that these automatic scroll point won’t work as custom stop points, in particular they won’t be configurable as they are virtual.
]]>
< ![CDATA[
But is it possible to turn off the automatic scroll stop option in order to use the manual ones. Or to set the automat ones to a lower priority so it automatically shuts off if manual stop points are added?
In refrence to new infinite scrolling abilities.
]]>
< ![CDATA[
Or possibly make the automatic scroll stop function automaticaly move the manual stop points. Instead of what its doing now. I assume its alot of work and none of it is important to me. Im just offering ideas. Ideas that I dont know how to implement cause I dont make apps.
So if automatic scroll stops are enabled 2 manual stop points are automatically created. One at the top left. And one at the top right and one at the bottom left. If an icon is dragged outside this area the two manual stop points are moved accordingly.
This could possibly be worked in with the command to automatically shrink desktop to items as well.
]]>
< ![CDATA[
In fact auto scroll stops work as if there was one scroll point on each page corner, however they are purely virtual and cannot be configured. The cool thing is that it avoids to do this manually on all pages. But using these features is somewhat equivalent to snap to pages and I wasn’t sure that this was useful to keep both.
]]>
< ![CDATA[
I am worried about future improvement of scrolling stop points : custom ones will receive a customization screen, for instance to select their direction, but auto scroll stops won’t be customizable this way, and I fear this will seem odd.
This also mean that I will have to keep the old code for auto scroll stops, while developing new custom ones. This is my problem though.
]]>
< ![CDATA[
The use case of Robert Posey is a valid one though, because this is the only screen with so many items.
]]>
< ![CDATA[
But could you rewrite the auto stop feature to move non virtual manual stops.
]]>
< ![CDATA[
Do the auto scroll stop points need to be virtual? Or is that just what they currently are.
You have done some pretty amazing stuff with LL and what ever features you add or remove im sure it will remain my favorite launcher.
]]>
< ![CDATA[
They need to because they are automatically generated depending on the current viewport. Thanks for your support 🙂
]]>
< ![CDATA[
Ok I believe I miss understood the purpose of auto scroll stops.
I thought it was the same as fit desktop to items.
It seems its purpose is to snap scrolling in single screen distances from the last desktop edge scrolled from?
Basicaly it dosent do what I thought it did and I dont believe I need it.
Sorry for the confusion. I was talking about fit desktop to page.
]]>