Skip to content
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

[wpf-graphics-rendering-overview.md] clarifying VisualTree traversal order #1943

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

glenn-slayden
Copy link
Contributor

@glenn-slayden glenn-slayden commented Dec 16, 2024

copyedit (medium): one paragraph, for your consideration and review.


Internal previews

📄 File 🔗 Preview link
dotnet-desktop-guide/framework/wpf/graphics-multimedia/wpf-graphics-rendering-overview.md dotnet-desktop-guide/framework/wpf/graphics-multimedia/wpf-graphics-rendering-overview

…traversal order

Copyedit one paragraph for your review.
@adegeo
Copy link
Contributor

adegeo commented Dec 18, 2024

Hi @glenn-slayden

I'll need to do some investigating on this PR as it's changing some of the wording that's very specific to behavior. I assume that when this content was originally written, it was done so with the product group. Like, why was "left to right" chosen as the phrase to communicate render order? Is it true? Does position factor into sibling rendering? I'll have to explore the code or find someone that knows more than myself.

Another example is that you introduced "child nodes are always rendered first" is that 100% without a doubt true? Or is this an assumption? Can something else in code or in behavior actually alter the order so that it isn't true? I don't know.

I'm curious, what's the motivation behind this PR?

@adegeo adegeo requested a review from a team December 18, 2024 18:14
@adegeo
Copy link
Contributor

adegeo commented Dec 18, 2024

@dotnet/wpf-developers

@glenn-slayden
Copy link
Contributor Author

Thanks for the feedback. As you can check my logs, I don't make many PRs, but when I do I hope the information is solid, especially when proffered to a serious commercial venture. I am a past MS SDE dev and have specialized in working on Visual/Drawing/DrawingVisual-level code for WPF since it started in 2007 or so. I even have a few "actually retained graphics" successes in this type of WPF design, which is admittedly off-the-beaten-path. Most people just stick with the Measure/Arrange layout pass model since it's easier and more comprehensible.

Retained-mode programming on WPF is not easy, but its reasonably capable and fantastically performant when it works. Just trying to improve things, but if my submission doesn't satisfy your standards then it's no offense.

@adegeo
Copy link
Contributor

adegeo commented Jan 6, 2025

Thanks for the response Glenn! I'll dive into this PR. The only reason I was questioning you is just the fact that there are so many AI bots that do these odd wording changes, so as soon as I start asking questions with no response I sort of get the idea.

My only concern is for myself, I just don't know that much about it to validate a submission in this area. Considering the holiday season is now over, I hope to get some of the WPF product group to look at it. From my point of view it seems solid, but I just want them to give a stamp of approval.

Thanks again, and I appreciate your thoroughness!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants