Update dependency com.patrykandpatrick.vico:compose-m3 to v2.4.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
com.patrykandpatrick.vico:compose-m3	2.2.0 → 2.4.1

---

Release Notes

patrykandpatrick/vico (com.patrykandpatrick.vico:compose-m3)

v2.4.1

Overview

• breaking changes: none
• addressed: #​1281

core

• Fixed an issue where CartesianMarkers could appear at the wrong x-value in CartesianCharts with an x-step other than 1.

multiplatform

• Fixed an issue where CartesianMarkers could appear at the wrong x-value in CartesianCharts with an x-step other than 1.

v2.4.0

[!NOTE]
For Android, the minimum SDK version has been raised from 21 to 23, in line with AndroidX.

Overview

• breaking changes: none¹
• addressed: #​1115, #​1202, #​1203, #​1218, #​1221, #​1217, #​1239
• external contributors: @​moonggae

core

• Added Interaction.Enter and Interaction.Exit.
• Added CartesianMarkerController.showOnHover.
• Added acceptsLongPress and lock properties to CartesianMarkerController.
• Prevented the x-values of CartesianMarkers from being clamped to the visible x-range.
• Fixed an issue where automatic scrolling wasn’t triggered on extra-only CartesianChartModel updates.
• Addressed an issue where CartesianMarkerController.ShowOnPress misbehaves when the CartesianMarker is shown and the x-value corresponding to its position changes. The fix required that the underlying CartesianMarkerController be made stateful, so CartesianMarkerController.ShowOnPress has been deprecated in favor of a CartesianMarkerController.showOnPress factory function.
• In MeasuringContext, deprecated canvasBounds in favor of canvasSize; see the deprecation message for more.
• In CartesianMeasuringContext, deprecated pointerPosition and isMarkerShown in favor of markerX; see the deprecation messages for more.
• Deprecated the existing CartesianChart.getMarkerTargets overload in favor of a new one, with x and visibleXRange parameters.
• Deprecated CartesianChartModel.id and CartesianLayerModel.id; see the deprecation messages for more.

compose

• Added CartesianMarkerController.rememberShowOnPress, CartesianMarkerController.rememberToggleOnTap, and CartesianMarkerController.rememberShowOnHover. Prefer these over the core equivalents.
• Updated CartesianChartHost to use Modifier.heightIn(max = 200.dp) instead of Modifier.height(200.dp) for its default preferred height. This retains the same behavior in most cases but ensures that an intrinsic height of 200 dp isn’t forced. For example, when a CartesianChartHost is placed in a Row with Modifier.height(IntrinsicSize.Min) alongside content with a specific intrinsic height, the height of said content is now used. In the unlikely case that undesired behavior changes occur, apply Modifier.height(200.dp) via CartesianChartHost’s modifier parameter. Externally passed height modifiers, including Modifier.height and Modifier.fillMaxHeight, continue to be respected.
• Resolved an issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized.
• Fixed an issue where a new CartesianChartHost linked to a CartesianChartModelProducer with a cached CartesianChartModel drew the CartesianChart with a delay, briefly showing the placeholder.
• Deprecated cartesian.cartesianLayerPadding in favor of the new cartesian.layer.cartesianLayerPadding, whose location matches that of CartesianLayerPadding in core.
• Deprecated the consumeMoveEvents parameter of CartesianChartHost; see the deprecation message for more.

views

• Resolved an issue where CartesianChartView mishandled padding, leading to incorrect CartesianChart rendering and Bitmap-related crashes.
• Resolved an issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized.
• Fixed an issue where a new CartesianChartView linked to a CartesianChartModelProducer with a cached CartesianChartModel drew the CartesianChart with a delay, briefly showing the placeholder.
• Deprecated the consumeMoveEvents property of CartesianChartView and the corresponding XML attribute; see the deprecation messages for more.

multiplatform

• Added web support (via Kotlin/Wasm).
• Added Interaction.Enter and Interaction.Exit.
• Added CartesianMarkerController.rememberShowOnHover.
• Added acceptsLongPress and lock properties to CartesianMarkerController.
• Updated CartesianChartHost to use Modifier.heightIn(max = 200.dp) instead of Modifier.height(200.dp) for its default preferred height. This retains the same behavior in most cases but ensures that an intrinsic height of 200 dp isn’t forced. For example, when a CartesianChartHost is placed in a Row with Modifier.height(IntrinsicSize.Min) alongside content with a specific intrinsic height, the height of said content is now used. In the unlikely case that undesired behavior changes occur, apply Modifier.height(200.dp) via CartesianChartHost’s modifier parameter. Externally passed height modifiers, including Modifier.height and Modifier.fillMaxHeight, continue to be respected.
• Prevented the x-values of CartesianMarkers from being clamped to the visible x-range.
• Resolved an issue where the x-values of semipermanent CartesianMarkers—such as those involving CartesianMakerController.toggleOnTap—could unexpectedly change when the CartesianChart was resized.
• Addressed an issue where CartesianMarkerController.ShowOnPress misbehaved when the CartesianMarker was shown and the x-value corresponding to its position changed. The fix required that the underlying CartesianMarkerController be made stateful, so CartesianMarkerController.ShowOnPress has been replaced with a CartesianMarkerController.rememberShowOnPress factory function.
• Fixed an issue where automatic scrolling wasn’t triggered on extra-only CartesianChartModel updates.
• Fixed an issue where a new CartesianChartHost linked to a CartesianChartModelProducer with a cached CartesianChartModel drew the CartesianChart with a delay, briefly showing the placeholder.
• In CartesianMeasuringContext, removed pointerPosition and isMarkerShown in favor of markerX; use markerX and markerX != null, respectively.
• Updated CartesianChart.getMarkerTargets to have x and visibleXRange parameters.
• Replaced CartesianMarkerController.toggleOnTap with CartesianMarkerController.rememberToggleOnTap.
• Removed CartesianChartModel.id and CartesianLayerModel.id in favor of equals and hashCode.
• Removed the consumeMoveEvents parameter of CartesianChartHost; use either the new consumeMoveEvents parameter of CartesianMarkerController.rememberShowOnPress or CartesianMarkerController.consumeMoveEvents instead.

v2.3.6

Overview

• breaking changes: none
• addressed: #​1160

compose

• An issue where the content of CartesianCharts could unexpectedly shift during zoom has been resolved.

views

• An issue where the content of CartesianCharts could unexpectedly shift during zoom has been resolved.

multiplatform

• An issue where the content of CartesianCharts could unexpectedly shift during zoom has been resolved.

v2.3.5

Overview

• breaking changes: none
• addressed: #​1160

compose

• An issue where the content of CartesianCharts could unexpectedly shift during zoom has been addressed.
• An issue where the content of CartesianCharts with unscalable padding drifted during zoom rather than remaining pinned at the pinch centroid has been resolved.

views

• An issue where the content of CartesianCharts could unexpectedly shift during zoom has been addressed.
• An issue where the content of CartesianCharts with unscalable padding drifted during zoom rather than remaining pinned at the pinch centroid has been resolved.

multiplatform

• An issue where the content of CartesianCharts could unexpectedly shift during zoom has been addressed.
• An issue where the content of CartesianCharts with unscalable padding drifted during zoom rather than remaining pinned at the pinch centroid has been resolved.

v2.3.4

Overview

• breaking changes: none
• addressed: #​1197

core

• An issue where some CartesianMarker.Targets could be missed when a CartesianMarker was drawn at an x-value with multiple CartesianMarker.Targets has been resolved.

multiplatform

• An issue where some CartesianMarker.Targets could be missed when a CartesianMarker was drawn at an x-value with multiple CartesianMarker.Targets has been resolved.

v2.3.3

Overview

• breaking changes: none
• addressed: #​1090

core

• In VerticalAxis, an issue where some labels were unnecessarily hidden when verticalLabelPosition was set to Position.Vertical.Top or Position.Vertical.Bottom has been resolved.

multiplatform

• In VerticalAxis, an issue where some labels were unnecessarily hidden when verticalLabelPosition was set to Position.Vertical.Top or Position.Vertical.Bottom has been resolved.

v2.3.2

Overview

• breaking changes: none
• addressed: #​1185

multiplatform

• An issue where the LineCartesianLayer.LineFill implementation instantiated by LineCartesianLayer.LineFill.single failed to fully fill lines that extended past the CartesianLayer area has been resolved. This happens, for example, when a line has a horizontal segment at the CartesianChart’s minimum or maximum y-value—in which case it’s centered at the corresponding edge of the CartesianLayer area, with half sticking out. The bug also caused problems with CartesianMarker color extraction.

v2.3.1

Overview

• breaking changes: none
• addressed: #​1198

compose

• An issue where CartesianMarkerVisiblityListener.onHidden was never called has been resolved.

multiplatform

• An issue where CartesianMarkerVisiblityListener.onHidden was never called has been resolved.

v2.3.0

Overview

• breaking changes: none¹
• addressed: #​356, #​465, #​574, #​769 comment, #​1060, #​1167, #​1171, #​1186

core

1. The new CartesianMarkerController enables granular control of CartesianMarker visibility. For example, with CartesianMarkerController.toggleOnTap, you can have a CartesianMarker show up only on explicit taps—not on gesture-starting presses—and remain visible until another tap elsewhere. For details, see the API reference. CartesianChart has a new markerController property, and the context parameter has been removed from the previously protected getMarkerTargets.
2. An issue where the axis lines of adjacent HorizontalAxis and VerticalAxis instances sometimes failed to fully overlap in the corners—resulting in jagged connections—has been addressed. In relation to this fix, in Axis, the existing drawUnderLayers and drawOverLayers functions have been deprecated in favor of new overloads with axisDimensions parameters, and an updateAxisDimensions function has been added.

compose

1. In connection with core change 1, rememberCartesianChart has a new markerController parameter.

multiplatform

1. The new CartesianMarkerController enables granular control of CartesianMarker visibility. For example, with CartesianMarkerController.toggleOnTap, you can have a CartesianMarker show up only on explicit taps—not on gesture-starting presses—and remain visible until another tap elsewhere. For details, see the API reference. rememberCartesianChart has a new markerController parameter, and the context parameter has been removed from the previously protected CartesianChart.getMarkerTargets.
2. ShapeComponent and LineComponent now support shadows; add them via the shadows parameters.
3. For simplicity, the custom Shape interface has been removed in favor of Compose’s. DashedShape remains available but now takes a Compose Shape. MarkerCorneredShape has been renamed to MarkerCornerBasedShape and takes a Compose CornerBasedShape as its base.
4. An issue where the axis lines of adjacent HorizontalAxis and VerticalAxis instances sometimes failed to fully overlap in the corners—resulting in jagged connections—has been addressed. In relation to this fix, in Axis, axisDimensions parameters have been added to drawUnderLayers and drawOverLayers, and an updateAxisDimensions function has been added.
5. An issue where the LineCartesianLayer.AreaFill implementations instantiated by single and double could misposition nonuniform Fills has been resolved.

v2.2.1

Overview

• breaking changes: none
• addressed: #​1162

core

• An issue where LineCartesianLayer data labels were entirely truncated in right-to-left layouts has been addressed.

multiplatform

• An issue where LineCartesianLayer data labels caused crashes in right-to-left layouts has been addressed.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Footnotes

1. Excluding multiplatform, which is experimental. (It will remain available, but breaking changes are more likely.) ↩ ↩²