1.0.0-beta10

This release marks another major release including several bug fixes and new features.

Features

• Added two new close function types to the HitogoController: closeByState and closeByAlert. closeByAlert is using the hashcode to determine the relevant alerts.
• Added new system inside HitogoController that will manage the visibility of alerts. Usually each alert is triggered by a source. Each source has a reason to show this alert. Therefore it makes sense to close the alert if the reason has changed. There are different use cases that one alert has been triggered by multiple sources (like network error). Showing an alert for each network error (if it has the same alert content) is rather inefficient and could annoy the users. Starting with beta10, the system is keeping track of the amount of sources connected to one alert and prevents showing duplicate alerts. The system is also only hiding the alert if no other sources are attached to it. Of course this won't change the behavior that the user could close the alert manually.
• Made addCloseButton protected to avoid misusing the api. addCloseButton is only used internally if the dismissible state requires a close button (for example for view alerts).
• Revamped the hashcode for alerts/buttons. It is now using different parameter from the alert/button to create it's hashcode.
• closeOthers (ViewAlertBuilder) is now default false. This parameter can be changed via allowOthers/closeOthers and is responsible whether to close all alerts of the same AlertType if this alert is in the process in getting visible. The typical expectation is that new alerts won't close already visible alerts (of the same type).
• Button (and close button) has the ability to show html based text.

Bugfixes

• Fixed a crash inside PopupBuilder that would have been caused by the exit transition object not correctly being checked.