-
-
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
Raise the EffectiveViewPortChanged
when a control is added to the tree that has already has a valid layout
#17570
Raise the EffectiveViewPortChanged
when a control is added to the tree that has already has a valid layout
#17570
Conversation
… being raised when it should. note: this tests are verified against UWP behavior.
You can test this PR using the following package version. |
Please read the following Contributor License Agreement (CLA). If you agree with the CLA, please reply with the following:
Contributor License AgreementContribution License AgreementThis Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ), 1. Definitions. “Code” means the computer software code, whether in human-readable or machine-executable form, “Project” means any of the projects owned or managed by AvaloniaUI OÜ and offered under a license “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any “Submission” means the Code and any other copyrightable material Submitted by You, including any 2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any 3. Originality of Work. You represent that each of Your Submissions is entirely Your 4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else 5. Licenses. a. Copyright License. You grant AvaloniaUI OÜ, and those who receive the Submission directly b. Patent License. You grant AvaloniaUI OÜ, and those who receive the Submission directly or c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement. 6. Representations and Warranties. You represent that You are legally entitled to grant the above 7. Notice to AvaloniaUI OÜ. You agree to notify AvaloniaUI OÜ in writing of any facts or 8. Information about Submissions. You agree that contributions to Projects and information about 9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the Republic of Estonia, and 10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and AvaloniaUI OÜ dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1. 2 out of 3 committers have signed the CLA. |
…ree that has already has a valid layout (#17570) * add unit tests to show that the EffectiveViewPortChanged event is not being raised when it should. note: this tests are verified against UWP behavior. * fix raising of EffectiveViewPortChanged event. --------- Co-authored-by: Julien Lebosquain <[email protected]> Co-authored-by: Max Katz <[email protected]>
What does the pull request do?
Fix the raising of the EffectiveViewPortChanged event.
What is the current behavior?
If you add a control that expects the
EffectiveViewPortChanged
event to a tree that has already has a valid layout, it never receives the event, giving the initial value.The reason is because when the listener is added
new EffectiveViewportChangedListener(
control,
CalculateEffectiveViewport(control));
When this is being added to a parent that has a size a size here is calculated.
Now when the actual layout pass happens
LayoutManager -> RaiseEffectiveViewportChanged()
viewport and l.Viewport are equal and the event is skipped.
What is the updated/expected behavior with this PR?
We now match the UWP behavior of raising the event.
How was the solution implemented (if it's not obvious)?
ViewPort
property.ViewPort
property nullable, so that it has to raise it the first time.This other PR updates the UWP tests that prove our behaviour is the same.
grokys/EffectiveBoundsTestsUWP#1
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues