CSharpMath.Rendering 0.5.0-beta

• .NETStandard 2.0

  • CSharpMath.Editor (>= 0.5.0-beta)
  • System.Numerics.Vectors (>= 4.5.0)

# 0.5.0 Evaluation Update Beta

## Changes from v0.5.0-alpha4 (Recently merged first)
## 🚀 Features

<details><summary>Add placeholder blinks setting (#177) @SymboLinker</summary><table><td>

In issue #175 a feature request was done for stopping the blinking of the placeholder (but still have a blinking carret if it moves to a spot without a placeholder).

The proposed pull request #176 just removes the blinking of the placeholder and does not leave it as an option.

This pull request adds a setting LaTeXSetting.PlaceholderBlinks that keeps the default value true and does not break any existing unit tests.

Tests are added
- to make sure that the setting for a non-blinking placeholder works
- to document how it should work
- to make sure that it will not be removed in a whim

@charlesroddie Please verify that the effect of changing the PlaceholderBlinks-setting results in the behaviour you like.
</td></table></details>

<details><summary>Make blinking Placeholder's Nucleus and ForeColor customizable in both CaretStates (#167) @SymboLinker</summary><table><td>

In pull request #164, posting https://github.com/verybadcat/CSharpMath/pull/164#issuecomment-699458440, the idea came up to make the placeholder customizable in the keyboard output. While PR #164 is concerned with the display of the keyboard buttons themselves, this PR is about the math keyboard output.

Currently the placeholder has two possible appearances: a full black square and an empty square with a black border.

This pull request makes the Nucleus and the ForeColor of the placeholder customizable in both CaretStates.

An example of usage: instead of an empty square with a black border in the 'hiding' CaretState, you could choose a full square with another Color (gray, for instance).

An example test:
In CSharpMath.Forms.Example\CSharpMath.Forms.Example\EditorPage.xaml.cs
add the following lines at the top of the constructor of the EditorView:
```
     Atom.LaTeXSettings.PlaceholderHidingNucleus = \u25A0;
     Atom.LaTeXSettings.PlaceholderHidingColor = Color.LightGray;
```
Open the Example project and go to the Editor tab. Click the fraction button. The output is:
where the square in the numerator blinks, LightGray/Black.

I am willing to write unit tests after some form of preliminary approval of this pull request.
(And of course I will fix mistakes and refactor if needed.)
</td></table></details>


## 🧰 Maintenance

- #180 take 2 (#181) @Happypig375

- Update Release workflow with the workaround from Test (#180) @Happypig375

<details><summary>Make MathKeyboard IDisposable (#179) @charlesroddie</summary><table><td>

fixes: https://github.com/verybadcat/CSharpMath/issues/178
</td></table></details>

<details><summary>Cleanup in preparation for Font Styles (#156) @charlesroddie</summary><table><td>

Initial simplification in preparation for adding Font Styles
- DoNothingFontChanger was removed was only used in tests.

For subsequent PR:
- UnicodeFontChanger uses mathematical bold/italic ranges to use a single font for normal/bold/italic. To preserve existing functionality without deploying additional fonts, this logic needs to be kept when using standard fonts.
- Allow users to add bold and italic fonts, for use in TextPainter. This PR will not address MathAtom fonts. If these fonts are present, they will be used instead of UnicodeFontChanger for rendering bold/italic fonts.
</td></table></details>

<details><summary>Enable the use of codecov.io (#163) @Happypig375</summary><table><td>

See https://codecov.io/gh/verybadcat/CSharpMath
</td></table></details>

<details><summary>Continuous Benchmark (#162) @Happypig375</summary><table><td>

See https://verybadcat.github.io/CSharpMath/dev/bench/
</td></table></details>

- Fix GitHub Packages (#157) @Happypig375

<details><summary>Add test coverage as CI artifacts (#155) @Happypig375</summary><table><td>

Also CSharpMath.Rendering.Tests baselines became smaller magically
</td></table></details>

## Contributors
@Happypig375, @SymboLinker and @charlesroddie