Some invalid journal data is now handled
Journals now use polymorphic deserialization
Added Event names to all journal events
Remove unused controllers
Status now shows alerts when taking damage
JournalService support more journals
Added enums to frontend, not quite working
Added More examples to Explorer component
* [Core] Visual improvements to notifications
- Notification title was previously missing; it's back!
- Fixed window and label backgrounds to be correctly/consistently transparent.
The click-thru bit is only partially working (transparent areas are click-thru).
* [Core] Reduce notification font size to avoid wrapping
Now that titles work, I noticed a few notification titles were wrapping. Examples:
- System Discovery Complete (from Evaluator)
- Minimum Distance Reached (from BioInsights)
To address, I made the following adjustments:
* Made the test notification title longer by adding the word "Popup" so it is now "Test Popup Notification".
* Reduced the Title font size to 20 (from 24).
* Moved the content box up to close the gap a bit.
* [Core] Exclude the notification popup colour picker button from themes
Noticed it was not the colour it should be and thought the setting was always being reset -- turns out the setting was correct, the button colour was not.
Here's a quick hack to fix.
* [Core] Further notification title tweaking
Now "System Discovery Complete" *actually* fits.
* [Core] Widen the native pop-up font selector so you can see variants
The previous width was a little bit narrow for the family of fonts like Segoe UI Variable...
The new width is 2x the original size and fits all fonts on my system and should do the trick for the moment.
While testing, I discovered that plugins that don't yet support sending the Coalescing ID were not mixing well because the default value of the ID is 0 -- which is also a valid body id. If the default is null, receivers can detect the absent value and apply a sensible default (ie. group them where it makes sense).
This proposes a *new method* on IObservatoryCore: `SetGridItems(worker, items)` which does 2 things:
* Clears the grid
* Adds the given items.
Effectively replaces the entire content of the grid -- which is something a handful of plugins now do.
Why add this when you could just call Core's Clear + AddGridItems methods?? So it can all be done within the same rendering suppression "scope" to reduce flickering and increase rendering speed. Speaking of rendering suppression, I have implemented such rendering suppression "scope" which uses Listview's built-in Begin/EndUpdate() in combination with temporary removal of the sort comparer (as is done for read-alls). This was also applied to the existing AddGridItems(worker, items) method as well, addressing a TODO.
Pre-reading is good. And turns out a number of plugins kinda depend on it now. Time to make it default.
Also, comment out settings upgrades so settings are carried over from version to version when running in the IDE -- which makes using it far better.
Just shuffled code within conditional compiler directives because when publishing, it seems "RELEASE" is not set. This ensures in the non PORTABLE case, the default path is set.
(Discovered while testing my publishing script with signing.)
Add checkboxes to the PluginList which allow you to enable/disable each plugin on-the-fly (it will no longer respond to events, but you can still configure it, etc.). These settings are preserved in a new Core setting. Also enabled full-row select for easier selection in the listview.
Also increased the height of the PluginList slightly. (Personally, I'd like it even taller.)
Also made slight sizing adjustments to the plugin tabs, which now show 3 letters when collapsed and has a bit of extra space so the longest one does not get cut-off when selected/bolded. Furthermore, the list of plugins is now sorted alphabetically.
Finally, set the plugin listview Dock = Fill (vs. Anchored). This seems to have fixed the listview resize problem I was experiencing.
* [Core] Settings improvements: Grouping w/labels, support for doubles
Layout improvements:
* Plugins can set `[SettingSuggestedColumnWidth(123)]` on a settings class to adjust the settings view column width to make it wider or narrower to fit things nicely.
* Plugins can set `[SettingNewGroup("label")]` on any setting property to force a "new paragraph", or group, of settings. If "label" is also provided, a grouping header with that text will also be created.
* A double precision up/down numeric control has been added. In support of this, there is now a precision value on the existing `[SettingNumericBounds]` attribute to specify the number of digits of precision the control displays/allows.
Plugins:
* The above have been applied/demonstrated on the Botanist and Explorer plugin settings.
This will allow notifications to be sent to Notification listeners during read-all to enhance testability.
This is controlled by the `DEBUG` compiler directive, so Release versions will not have this behaviour.
However, Herald, being a plugin itself, should ignore these otherwise the results are.... unfortunate. #askmehowiknow
