This pull request is somewhat big, and switches over the list implementation to a ListView + ListAdapter style.

This accomplishes two important things:

• It brings the API to be more in line with a real dialog (think setAdapter() and getListView())
• Dramatically improves list scrolling performance due to not inflating all views upfront.

The basic structure of this is that it uses a new in-house adapter called MaterialDialogAdapter for first-party list options (single, multi, and regular). For custom adapters (set via .adapter() in the Builder), it delegates their logic to the user's implementation (like a real dialog!).

This also improved performance of handling callbacks, as now we can retrieve the item directly rather than iterate over the inflated views to find the selected one.

Here's a short screen record going through the list items in the sample: https://www.dropbox.com/s/gs8qn6ytrktrc6d/device-2014-12-01-182852.mp4?dl=0

NOTE: This removes the ItemProcessor API, as it's now unnecessary since users can build the dialog with their own (much more flexible) adapter.

I made a couple other minor changes when I saw them, like c2ad109

I added a simple argb color selector and fixed this bug: https://github.com/afollestad/material-dialogs/issues/1627

I kept it quite simple, let me know what you think of it

Lollipop's alert dialogs respect the current theme's android:textAllCaps attribute. It would be great if these did too. I don't know if there is any other way to override this.

The previous setup was causing lag when showing or updating the dialog, because it needed to wait until everything was laid out before adjusting the padding, which would trigger a second layout.

This method uses a custom ViewGroup (MDRootLayout) which determines padding and button stacking onMeasure.

Changes were also made with how the padding was split up, to avoid having to move padding between views.

This pull request allows setting maximum icon size through the following methods:

• to a default limit of 32dp (based from the platform AlertDialog)
  • limitIconToDefaultSize() builder method
  • md_icon_limit_icon_to_default_size global theme attribute
• to a specified maximum size
  • maxIconSize(int maxIconSize) builder method
  • md_icon_max_size global theme attribute

This feature was requested in #297.

Some windows with just the right amount of scrollable content would trigger the removal of the bottom margin, however the new layout pass would show that the content is no longer scrollable so the bottom margin would be reenabled. This would cause the window to continously vibrate up and down.

This fix verifies the available space before adding the margin, and doesn't add it, if it would cause the content to scroll.

https://github.com/afollestad/material-dialogs/issues/100 Added some global attributes such as

<item name="md_custom_theme">true</item>
<item name="md_bg_color">#673AB7</item>
<item name="md_divider_color">#673AB7</item>
<item name="md_selector">@drawable/selector</item>
<item name="md_btn_selector">@drawable/selector</item>

New attribute md_bg_color, md_divider_color, md_selector, md_btn_selector will be enabled only if md_custom_theme is true.

We can also set new attributes programmatically.

public Builder backgroundColor(int color)
public Builder backgroundColorRes(@ColorRes int colorRes)
public Builder dividerColor(int color) 
public Builder dividerColorRes(@ColorRes int colorRes)
public Builder selector(@DrawableRes int selector)
public Builder btnSelector(@DrawableRes int btnSelector)

If we don't set default for each attribute while using custom dialog, the default light or dark theme will be set as default. For example, when md_dark_theme is true and md_custom_theme is also true, but md_bg_color hasn't set yet, the background color might follow background color of md_dark_theme.

This pull request adds an EditText to the dialog.

• Turn it on through a Builder method.
• Specify EditText hint
• Provide a default value to pre-fill the EditText with
• Set a TextWatcher on the EditText to be informed of changes to the text
• Provide a callback to be informed of the text when the positive button is pressed
• Perform input validation on the entered text
  • Provide a validator class to use
  • Specify an error message to display when the input is invalid
  • Error appears as message below the EditText, there is option to instead display it in little popup with error icon (standard EditText setError(String) method.
• EditText is tinted (color filter used for pre-Android 5).

Title bar no longer scrolls with custom content There is no longer a seperate titlebarframe for custom content Added top divider when content scrolls

It's a bit of an invasive change so let me know if it breaks anything or something isn't done in the style you'd prefer.

Fixes https://github.com/afollestad/material-dialogs/issues/45

... but there were other action buttons. If there is a positive button it will be used to trigger the callbacks. But when it is not present, the callbacks need to be called on each change produced by a click since no click on a positive button will trigger them.

This is to support About Libraries, a library to facilitate listing dependencies. Your project is currently embedded in that project, which means the version number needs to be manually changed. Having it in your project directly along with the resValue in gradle will make this automatic.

These resources will be removed if users have proguard. Those who choose to use about libraries with proguard will keep the R classes to resolve that.

Attached below is an example of how it looks. (Note that the UI can be customized, but the text will be the same throughout projects)

Guidelines

1. You must run the spotlessApply task before commiting, either through Android Studio or with ./gradlew spotlessApply.
2. A PR should be focused and contained. If you are changing multiple unrelated things, they should be in separate PRs.
3. A PR should fix a bug or solve a problem - something that only you would use is not necessarily something that should be published.
4. Give your PR a detailed title and description - look over your code one last time before actually creating the PR. Give it a self-review.

If you do not follow the guidelines, your PR will be rejected.

Feel free to only merge the bottom sheet changes and the dismiss change.

This does fix following issue: https://github.com/afollestad/material-dialogs/issues/2076

Changes

• Updated MaterialDialog dismiss function to make sure it's only called if the activity is not being finished (only if it is attached to an activity and only on android API >= 17)
• Updated BottomSheet to allow to enable/disable animation and to allow to define an initial state (half expanded, full expanded) => animation must be disabled inside a DialogFragment because this fragment will call onShow after screen rotation and also after screen off/on => this leads to collapsed sheets sometimes and to repeated animations on every screen on/off => if animation is disabled, everything works perfectly fine inside a DialogFragment as well now

Additionally I would have also done following:

• updated gradle to 7.2
• made the project jitpack compatible again after update to gradle 7 (forks can be retrieved easily via jitpack now)
• made the project compatible to include it as local fork
  • added a "namespace" to all modules (prefix md)
  • made gradle definitions relative to project instead of root project

TODO after merge (seems like you do not merge anything anymore, but still here are the steps to undo my "special" changes)

• Change the maven config back to yours: https://github.com/MFlisar/material-dialogs/blob/b8f8203513466b1c30dc8046ef5e61a3e61495b5/gradle/android_library_config.gradle#L6-L9
• Enable spotless again (I don't use spotless and so I disabled this plugin, it does not work out of the box in a local fork the way its set up in your repo) https://github.com/MFlisar/material-dialogs/blob/b8f8203513466b1c30dc8046ef5e61a3e61495b5/gradle/android_common_config.gradle#L6

Note

If someone else wants to use it already, it's already published on jitpack and can be used like following:

implementation "com.github.MFlisar.material-dialogs:core:3.3.0-1"
....

Updated the sw600dp dimens.xml file to make the dialog's text readable in a tablet's screen. New text size was tested in several tablets.

Guidelines

1. You must run the spotlessApply task before commiting, either through Android Studio or with ./gradlew spotlessApply.
2. A PR should be focused and contained. If you are changing multiple unrelated things, they should be in separate PRs.
3. A PR should fix a bug or solve a problem - something that only you would use is not necessarily something that should be published.
4. Give your PR a detailed title and description - look over your code one last time before actually creating the PR. Give it a self-review.

If you do not follow the guidelines, your PR will be rejected.

Guidelines

1. You must run the spotlessApply task before commiting, either through Android Studio or with ./gradlew spotlessApply.
2. A PR should be focused and contained. If you are changing multiple unrelated things, they should be in separate PRs.
3. A PR should fix a bug or solve a problem - something that only you would use is not necessarily something that should be published.
4. Give your PR a detailed title and description - look over your code one last time before actually creating the PR. Give it a self-review.

If you do not follow the guidelines, your PR will be rejected.

PR Description

Changed logic regarding minDate and maxDate in dateTime module to allow currentDate to be equal to one of them. This is to make it possible to have two dates as allowed dates, and preselect one of them, which was not possible before. The user was able to select one of the two dates, but the code was not allowing preselection of the dates. For example with these dates:

minDate = 2021.01.01
maxDate = 2021.01.02
currentDate = 2021.01.01

Issues #2036 and #1973 refer to crashes when minDate or maxDate are equal to currentDate in the datetime module datePicker. This request changes the checks for minDate and maxDate validity to allow for these dates to also be the currentDate.