Plus Edition. Incorrect window position restoration after returning from the maximized state.
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
Research direction
Start in Child_MaximizedChanged and compare the supplied current and corrected code paths. Reproduce the child-window sequence by moving it, maximizing it, and restoring it; done means the prior Left and Top are restored while the window remains restricted to the valid container area.
Written by the indexing model from the issue text.
Description
Sequence of actions:
- Child window. Left > 0 and Top > 0.
- Maximize the window to full screen.
- Restore the window position to the previous state.
Left = 0 and Top = 0. That is, the previous position is not restored.
Source code:
private void Child_MaximizedChanged(object sender, EventArgs e) {
...
WindowContainerChildData initialData = (WindowContainerChildData)windowControl.InitialData;
windowControl.Left = initialData.Left;
windowControl.Top = initialData.Top;
windowControl.Width = initialData.Width;
windowControl.Height = initialData.Height;
windowControl.UpdateLayout();
windowControl.Left = this.GetRestrictedLeft(windowControl);
windowControl.Top = this.GetRestrictedTop(windowControl);
}
}
Corrected code:
private void Child_MaximizedChanged(object sender, EventArgs e) {
...
WindowContainerChildData initialData = (WindowContainerChildData)windowControl.InitialData;
windowControl.Width = initialData.Width;
windowControl.Height = initialData.Height;
windowControl.UpdateLayout();
windowControl.Left = initialData.Left;
windowControl.Top = initialData.Top;
windowControl.Left = this.GetRestrictedLeft(windowControl);
windowControl.Top = this.GetRestrictedTop(windowControl);
}
}
- Dominant language
- C#
- Stars
- 4.2k
- Forks
- 912
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from xceedsoftware/wpftoolkit
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
xceedsoftware/wpftoolkit#1808 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
xceedsoftware/wpftoolkit#1807 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
xceedsoftware/wpftoolkit#1806 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
xceedsoftware/wpftoolkit#1802 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
xceedsoftware/wpftoolkit#1801 · 2 comments ·
All issues in xceedsoftware/wpftoolkit
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·