-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add TextBlock inlines support #6953
Add TextBlock inlines support #6953
Conversation
e941c1e
to
0e398a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just some nits but lgtm! :D
Question: With this level of support for text formatting do you think it's feasible to start looking at RichTextBox (from WPF) or MarkdownTextBox (from UWP toolkit) control ports? Not asking you to look into it, just do you think it's going to be possible soon? It would be great to see those controls eventually at least in 3rd party libraries to start and it seems with all your text improvements it's getting close to possible. |
To be able to port RichtTextBox we need #5461 that introduces all the required infrastructure. MarkdownTextBlock needs InlineUIContainer support. That will be added soon. |
/// <summary> | ||
/// Raises the <see cref="Invalidate"/> event. | ||
/// </summary> | ||
protected void Invalidate() => Invalidated?.Invoke(this, EventArgs.Empty); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A system of Debouncing could be implemented, so that when there are changes in rapid succession the event is called only once.
f2c24f2
to
4b89cb6
Compare
Good job, @Gillibald ! Awesome news! I will merge this to our app fork and will provide a feedback from our QA Team in a week or so. |
Please note that XamlX needs to be updated to deal with inlines properly. |
In WPF if there is any empty space between |
|
|
I will add some unit tests that use Static/DynamicResource for some inlines properties. |
@Gillibald I want to merge your fixes and test them but auto-build is failed. so I'm a bit scarry to invest a time into this. |
The build fails because of one Xaml test that is failing. So it should not affect you. |
Thanks for testing. So we need to add a test for comments and get transitions working. |
0536858
to
eb5ad8e
Compare
@Mikolaytis Everything should work now |
eb5ad8e
to
2b9dfc3
Compare
@Gillibald one more thing is broken We've found - TextAlignment=Right on a textbox now broken. Text Measure looks like returning a 0 width. |
also we're still testing and it's possible we will find something more this year. |
I wonder how that is possible. Will investigate. |
1862494
to
e190f91
Compare
eec8721
to
9e2773e
Compare
You can test this PR using the following package version. |
52d78df
to
95769ff
Compare
You can test this PR using the following package version. |
You can test this PR using the following package version. |
1 similar comment
You can test this PR using the following package version. |
Is there a chance to backport this in 0.10.x ? |
No, too many breaking changes to get this work with whole new text layout system.
Hopefully, first preview will be in the end of this month or beginning of the next. Expected to get first third party libraries to support this version too. |
What does the pull request do?
With updated XamlIl
What is the current behavior?
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues
Fixes #3737 #2619