This section documents all changes and bug fixes applied to MySQL Notifier since the release of 1.1.4.
Functionality Added or Changed
Notifier now automatically detects when Workbench is installed or uninstalled, and starts or stops monitoring its files, depending, which no longer requires MySQL Notifier to be restarted.
MySQL connections can now be edited from within MySQL Notifier, and no longer requires MySQL Workbench to be installed.
The MySQL Utilities can now be opened from MySQL Notifier.
After executing Action, Manage Monitored items, Instance, and then Add MySQL Instance, clicking Cancel would generate an unexpected fatal error. (Bug #17697914)
MySQL Instances linked to workbench connections were not removed automatically when MySQL Workbench was uninstalled. (Bug #17671410)
A "High Severity Error" would be generated at startup if MySQL Installer attempted to install the MySQL Server and MySQL Notifier, and failed to install the MySQL Server. (Bug #17432516, Bug #70282)
On Windows XP, if the current user lacked credentials to schedule tasks, the MySQL Notifier startup task was not scheduled after it was installed. (Bug #14388579)
The SQL editor submenu did not automatically refresh when connections were added or removed outside of MySQL Notifier while it was running.
Reinstalling MySQL Workbench would cause duplicate connection entries to be listed in MySQL Notifier.
Installing a MySQL Notifier package when a previous version of MySQL Notifier was installed could corrupt the configuration file.