-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Bug] ContentPage.ControlTemplate gets not rendered in Wpf (#7671) #7728
Conversation
Is there a better solution? Because in the Please, have a closer look to my changes. |
{ | ||
public class FormsContentPage : FormsPage | ||
{ | ||
public FormsContentPage() | ||
{ | ||
this.DefaultStyleKey = typeof(FormsContentPage); |
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.
Why not using the FrameworkPropertyMetadata?
What is missing? What is wrong? |
@neolithos Could you rebase master to fix the conflict, please? |
deleted I found out, what I did wrong. It should be correct, now. |
I rebased this a more than ones since 2019. But how do I solve this:
|
Style issues Layout was applied on the content and not the visual first child Fix: typo Shared project fix Xml-Tag Fix for issue xamarin#7671 Style issues Layout was applied on the content and not the visual first child Fix: typo
a6b4020
to
5dc6752
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Epic! It took a little while (🤏 ) but finally got to look at this. It works for the Xamarin Community Toolkit sample app! Thanks for this great contribution! |
That was long... |
At least it wasn't never! 🎉 |
Description of Change
PageRenderer
renderes the first child instead of theContent
.Sorry, I destroyed the branch #7672.
Issues Resolved
API Changes
None
Platforms Affected
Behavioral/Visual Changes
ControlTemplate gets rendered in wpf.
Before/After Screenshots
Before:
![PageRendererBefore](https://user-images.githubusercontent.com/9724420/65603918-d43f6380-dfa6-11e9-8a8f-6daa2bfa2ebe.png)
![PageRendererAfter](https://user-images.githubusercontent.com/9724420/65603915-d43f6380-dfa6-11e9-8540-43706d68e349.png)
After:
PR Checklist