1.0.8

Progress Dialog uses a composable for its content now

1.0.7

Compose Version: 2024.04.00

DialogInputNumber does support a formatter and validator now.

Full Changelog: 1.0.6...1.0.7

1.0.6

• updated compose bom: 2024.02.01 => 2024.03.00
• DialogList - SingleSelect mode: closeOnSelectionChanged was changed to closeOnSelect

Full Changelog: 1.0.5...1.0.6

1.0.5

• updated compose bom: 2023.10.01 => 2024.02.01
• versions updated to latest stable
• DialogList - SingleSelect mode: extended with option closeOnSelectionChanged

Full Changelog: 1.0.4...1.0.5

1.0.4

• updated compose bom: 2023.10.00 => 2023.10.01
• string resources added (DE + EN)]
• moved datetime packages to date/time respectively
• billing dialog added

Migration:

• import com.michaelflisar.composedialogs.dialogs.datetime.* is split up into import com.michaelflisar.composedialogs.dialogs.date.* and import com.michaelflisar.composedialogs.dialogs.time.* to follow the modules

1.0.3

Changes

• moved sub classes for dialogs into objects with the name of the dialog (e.g. DialogColor.Setup, DialogDate.Setup, ...)
• moved some init functions into DialogDefaults object
• rememberDialog functions use same parameter naming convention now

Improvements

• added some missing default values to ListDialog
• added second step size to number picker dialog
• cleaned up DateTimeUtils and changed all Calendar based functions to LocalDate
• changed date formatters to lambdas that work with LocalDate formatters by default now

1.0.2

• moved date/tme dialogs to LocalDate and LocalTime instead of custom classes
• date dialog does now correctly handle year changes via year selection and keeps the selected month in this case

1.0.1

exposed the checkerboard drawable function from DialogColorUtil - so that I can reuse it inside ComposePreferences... and because this probably is useful for anyone who wants to show a color the same way as the dialog does it anywhere outside the dialog

1.0

switched dialog text and icon from texts with setup to composables as this is the standard for those types and is more generic and easier to customise by the user

Necessary, because I decided that ComposePreferences uses this model as well and so I want both libraries to be structured the same and this makes the usage of the dialogs inside the preferences library easier

0.9

missing default value added to DialogInputNumber