Bug: Column thickness and spacing changes depending on the data count

This is the preview I get from Jetpack Compose, you can see that the more the data displayed, the smaller the column is.

Expected behavior Column thickness and spacing should be consistent regardless of how much data is displayed, if the data is too much to display in the screen, then it should be horizontally scrollable.

Code:

Chart(
    chart = columnChart(
        columns = listOf(
            LineComponent(context.getColor(R.color.primary), 1f, shape = pillShape),
            LineComponent(context.getColor(R.color.secondary), 1f, shape = pillShape),
        ),
        dataLabel = textComponent {
            typeface = Typeface.SANS_SERIF
            textAlign = Paint.Align.CENTER
            color = android.graphics.Color.WHITE
        },
        dataLabelVerticalPosition = VerticalPosition.Bottom,
        spacing = 4.dp,
        innerSpacing = 0.1.dp
    ),
    model = entryModelOf(frequencies, remainingStocks),
    startAxis = startAxis(
        label = axisLabelComponent(typeface = Typeface.SANS_SERIF, textSize = 10.sp, lineCount = 1),
        axis = null,
        tick = null,
        guideline = axisGuidelineComponent(shape = Shapes.rectShape, color = Color.LightGray.copy(alpha = .25f)),
        valueFormatter = DecimalFormatAxisValueFormatter("##")
    ),
    bottomAxis = bottomAxis(
        label = axisLabelComponent(typeface = Typeface.SANS_SERIF, textSize = 10.sp, lineCount = 1),
        guideline = null,
        tick = null,
        axis = null,
        valueFormatter = { value, _ -> labels[value.roundToInt()] }
    ),
)

[ghost]

Hello! Vico 1.6.0, which is now rolling out, adds the feature in question. Thank you for the suggestion!

[ghost]

I’ll add the parameter in question as soon as possible. Regarding thicknessDp, it’s not so much the minimum width as it is the intrinsic width. It’s multiplied by thicknessScale in the draw* functions of LineComponent. The factor can be greater than 1, equal to 1, or smaller than 1. We’ll discuss renaming the field to intrinsicWidth. Cheers for the context and the suggestion!