You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recommend you hide the second view layout, since it's only used as a placeholder for the end destination.
The views can be of any type, you can mix and match them, the two layouts can have a different number of views and nested layouts are 100% supported. The only things to keep in mind are:
all views which you would want to match together must have the same tag attribute in both layouts
all unmatched views will remain at their original place inside the original layout
the second layout is just a placeholder. It doesn't hold any logic, it only shows where the original layout should move to.
transition.duration =500
transition.interpolator =AccelerateDecelerateInterpolator()
transition.animateTo(percent =0f)
transition.onProgressChanged {
//triggered on every progress change of the transition
seekBar.progress = (it *100).toInt()
}
val progress:Float= transition.currentProgress
Here is a preview of a simple application made using this library
This effect can be reproduced by placing the "Transitioner.setProgress(Float)" function inside a onTouch or a onProgressChanged method.