search

maykar / lovelace-swipe-navigation

↔️ Swipe through Lovelace views on mobile.
MIT License
205 stars 70 forks source link

Swipe and fade animations speed increase possible? #19

Open recklessnl opened 4 years ago

recklessnl commented 4 years ago

First of all, fantastic work on this card, this makes the mobile lovelace frontend so much more usable. Great work!

I have a minor request: can you make it an option in the lovelace yaml to set the fade and swipe animation speed? I like both of the animations but they feel too slow / sluggish, and I would greatly prefer to edit the animation speed in order to make it feel snappier.

BoneheadFraggle commented 4 years ago

I second this. The functionality is great, but I just switched from CCH which was faster. And just after a few minutes use, I miss that speed. So, I also would like a shorter animation/faster speed. Preferably configurable :-)

That said - thanks a lot! CH + Swipe are really great features.

maykar commented 4 years ago

This is absolutely something I will add, either in the next release or soon after.

KTibow commented 4 years ago

Also maybe harder to make, but you could make it so it moves with the finger, instead of showing the set animation after the finger has moved enough.

maykar commented 4 years ago

Unfortunately, the new page needs to load each swipe. So it needs a bit of time to do so before appearing on screen. While it can be faster/slower it wouldn't work out well as a 1:1 finger to swipe.

fti7 commented 3 years ago

Im using this with the Android Companion App. Unfortunately it doesnt really "feel" native with the current approach. Wouldnt it be possible to Preload all Tabs/Pages and then only resume Value Updates after swipe for the specific Tab?

maykar commented 3 years ago

Not really possible with a custom addition like this. This doesn't "feel native" because it's not. What you're suggesting is better suited to be built into core or the companion apps themselves. But using the approach of "load all views" would significantly increase loading times and degrade performance (one reason I believe this still doesn't exist in core). It would be far better to load the next and previous views, but that still comes with a decent performance cost (and couldn't keep up with fast swiping).