-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.1.0-pre10, 0.1.0-rc.0, 0.1.0-rc.1, 0.1.0-rc.2 and 0.1.0-rc.3 have been released. #17
Comments
Nuget puts "0.1.0-pre10" between "0.1.0-pre1" and "0.1.0-pre2". |
I re-read the SemVer homepage. I didn't know I had to put a dot between |
0.1.0-rc.0 has been released. Please comment for any issues found. |
0.1.0-rc.1 has been released. Subpixel rendering looks to require extra work so it will get its own release candidate. Please report any issues. |
We will test. Subpixel can be moved to backlog if you prefer. |
On rc.0 I am getting for TextPainter that @"\blue{a}" shows a in blue, but @"\blue{$a$}" has a in black. |
Fixed on 0.1.0-rc.2. Subpixel will be in 0.1.0-rc.3. I don't want to move it to the backlog because it will greatly affect image-based unit tests later on. |
@Happypig375 seems like there is a problem with colors. Text like this |
0.1.0-rc.3 has been released. If there is no issues found within a few days, it will be the same as 0.1.0. |
Superceded by #21. |
It's time to have a new schedule. The old issue is getting hard to follow.
WIP:
To be in 0.1.0-rc.0
TextPainter
To be in 0.1.0-rc.1
The milestones below have been changed to after merger with wpf-math. Those shown are the original plan.
To be in 0.1.0-rc.3
Documentation before release
Scheduled 0.1.0 release
Between 0.1.0 and 0.2.0
Will most probably be pushed to 0.2.0
1 \\ { 2 \\ 3 }
's spacing between 1 and 2 is weirdHowever, it is also not yet complete as in not being able to SeparateThisReallyLongWordWhichIsSoLongThatItSpansAcrossTheEntirePageAndWontStopEvenWhenPartOfItIsOutOfBounds.
Will definitely be pushed to 0.2.0
(The unit tests will be dependent upon CSharpMath.SkiaSharp; and validated through picture comparisons)
Merged issue: #15
The text was updated successfully, but these errors were encountered: