Feature request: Listener for state changed about expandablelayout HOT 7 CLOSED

Thanks for the feedback, I'll work on it.

Regarding checking the expandedFraction, it should always return the correct value, unless you're using a Bounce or Overshoot interpolator. If that's not the case then it might be a bug which I'd like to fix.

By the way, checking the expansionFraction value in the listener should have no impact on performance unless you're doing something else in every check. A float compare is trivial work for a modern (even mobile) CPU.

from expandablelayout.

From my check, the expansionFraction param returns value from 0 to almost 1 (~0.9998...), but not 1, so I need to do some extra work to assume that it's closest to 1. A set of listeners to specific states would be very helpful. Anyway, thanks for the information.

from expandablelayout.

You're right, I just checked the code and internally I also had to work around the fact that the animator doesn't always reach 1.
I've opened ticket #33 to track this.

from expandablelayout.

Hi, i've tested my code and it works fine. 0 and 1 values were reached w/o problems. Link to gist
The result is:

• to open

data body was isCollapsed
expanding expansionFraction = 1.0
dataBody expending

• to close

data body was isExpanded
collapsing expansionFraction = 0.0
dataHeaderExpanded collapsing

P.S. Thanks for lib!

from expandablelayout.

@Savrov I think the problem doesn't occur on all interpolators. As far as I remember it works fine on the default one, which would explain why it's working for you.

from expandablelayout.

Fixed in 2.9

from expandablelayout.

Thanks a lot, it works now

from expandablelayout.