Closed PaulWoitaschek closed 8 years ago
When you call setNumericTransformer()
the max has already been set from the constructor so it will always use the current max value. Anything else I'm missing there?
The second part, changing the max value in a later time is true and I can fix it by calling updateSizes
as you suggest.
When using
setNumericTransformer
with a customtransformToString
, the library probes for the max and determines the size of the bubble by a call tomIndicator.updateSizes
using the current max value. The problem is that ifsetNumericTransformer
is called on initialization, the max has not been set and thus is 100. So the bubble has the wrong size. Also when you later change your seekbars max value, the value does not get updated and the bubble stays at the wrong size. So my suggestion is to simply update the indicator size by a call onmIndicator.updateSizes
insetMax
.