Skip to main content

2.0.0-alpha.21

This release introduces DefaultCartesianMarker.LabelPosition.Bottom and includes fixes and improvements.

Breaking changesAddressedContributors
Minor#670, #701, #705, #711, #724@L-Andrade

CartesianMarker​

The following changes have been made:

  • A new DefaultCartesianMarker.LabelPosition constant, Bottom, has been added. This positions the label below the CartesianLayer area.
  • We’ve addressed an issue where, for multi-series ColumnCartesianLayers with MergeMode.Grouped, CartesianMarkerVisibilityListener#onMoved wasn’t called when a CartesianMarker was moved from one column in a group to another.
  • In CartesianMarkerVisibilityListener, onMoved has been renamed to onUpdated, as this better reflects when the function is invoked. onMoved is deprecated.
  • In DefaultCartesianMarker, all properties are now read-only (val), and their visibility has been changed to protected. All of the same settings are available, but they should be changed via the parameters of rememberDefaultCartesianMarker. (Previously, there was a mix of val and var, and the properties’ visibility was public. This was left over from when some of the properties weren’t constructor properties.)

VerticalAxis​

The following issues have been resolved:

  • Labels were sometimes unexpectedly truncated.
  • With HorizontalLabelPosition.Inside, excessive horizontal insets were requested, creating unwanted empty space.
  • The default AxisItemPlacer.Vertical implementations misbehaved when BaseAxis#label was null, causing OutOfMemoryErrors.

ColumnCartesianLayer​

We’ve fixed an issue where ColumnCartesianLayer could throw an IllegalStateException (“Each entry’s x value must be a multiple of the x step”) when it shouldn’t have. This was related to Float imprecision.