Open CazimirRoman opened 6 years ago
Did you find a solution to the problem?
I'm facing the same issue with this, I'm trying to figure out why... if I find something, I'll post it here!
I found a "kind-of-workaround"... By using databinding for the visibility, it seems it works properly.
I suppose the rendering phase when it isn't applying the visibility you set in the xml (or in the onCreate/onResume or wherever you are setting the visibility dynamically) is in the very beginning. So, using databinding, it updates the visibility state later, and it applies it correctly.
Anyway, I just realised this library hasn't been updated for a couple years.
This does not seem to be an issue in 2.3.0
I suspect this commit to the 2.3.2 release to be causing the issue: https://github.com/Bearded-Hen/Android-Bootstrap/commit/0edd1ae7271fc680792d5bbefab8ee9582ed6db9
Have not fully investigated it but looks as if a non-empty string will cause AwesomeTextView to have visibility set to VISIBLE, not considering if it was set to GONE or HIDDEN.
Hi,
Calling setVisibility(View.GONE) or setVisibility(View.VISIBLE) does not have any effect on a BootstrapButton object. Also setting these flags in the XML does not change the visibility. The only option as I see it is to change the width to Odp. Thoughts?