Version 2.1 is out!

[almostearthling]

🚀 When version 2.1.1

What's New

This release features the following updates:

• conditions that are activated by the verification of other conditions can now be defined: this was once known as confluence in the old version of When and was implemented as a plugin for the wizard UI (that heavily relied on temporary files and the Python global interpreter lock);
• the new TOML 1.1.0 specification is supported: even though this is not a big step forward, it can really help in building more maintainable configuration files; 🎉
• speaking of the configuration file, now the private items (the ones that When manages automatically and whose names begin with the __When__private__ prefix) are located in the lower part of the configuration file, introduced by a TOML comment that suggests not to modify the configuration after the comment line.

Confluence conditions are now part of the standard When implementation, although they will not be available if the installed whenever binary does not support the necessary options. These options, however, are supported by the standard binary distribution (that is, the one compiled with the standard features for the specified platform), which is in fact the one provided along with each release.

What's Better

The following issues are now fixed:

• before just carelessly deleting an item if the user confirms it, When now checks for item dependencies (of events from conditions, and of conditions from tasks) and, in case such dependencies have actually been found, an error box is displayed to invite the user to resolve those dependencies,
• the path to the Lua initialization script is now rendered as a TOML literal string in the configuration file, which makes it more readable especially on Windows,
• the Windows version no longer displays an evanescent console window at startup, 👻

along with string and localization amendments, and other smaller interventions that concern both code clarity and, in some cases, optimizations. The last two fixes are probably minor ones, but needed anyway in the name of a smoother user experience. The first one addresses a more serious problem, in fact, because until this check and the related enforcement (no item can be deleted accidentally if there are active dependencies) When has been able to create configuration files that whenever would refuse, because it enforces this check at each reconfiguration, in contradiction with what is stated in the documentation.

Note

It is necessary to edit the configuration through the UI (no actual editing is needed: it is sufficient to recall an item, click the OK button instead of Cancel, and then save and overwrite the configuration) in order to benefit of the changes introduced in this release; an old-style, unmodified configuration, in this particular case, does not affect the functionality of the configured items.

Instructions

Please refer to the suggested instructions for installation. The packages with a latest suffix are exact copies of the ones generated by GitHub.

Warning

Note that at least version 1.2.0 of whenever is needed for this release to work.

---

This discussion was created from the release 2.1.1.