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

Fix ResizeMode of NoResize #347

Merged
merged 1 commit into from
Sep 15, 2022
Merged

Fix ResizeMode of NoResize #347

merged 1 commit into from
Sep 15, 2022

Conversation

FreeTheTech101
Copy link
Contributor

This PR fixes ResizeMode of NoResize not working when using ui:UiWindow.

Pull request type

  • Update
  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes

What is the current behavior?

Currently, setting the ResizeMode to NoResize does not work without also setting the WindowStyle to None. However, doing so breaks theming.

Issue Number: #324, also possibly #109, #202, and #207

What is the new behavior?

A conditional check has been added to the WindowChrome initializer, which checks to see if the ResizeMode is set to NoResize. If it is, the ResizeBorderThickness on the new WindowChrome receives a thickness of 0, which prevents resizing. Otherwise, default behavior is maintained.

Add a conditional check to our WindowChrome initializer to only apply a ResizeBorderThickness when the ResizeMode is not set to “NoResize”
@U-C-S
Copy link
Contributor

U-C-S commented Sep 14, 2022

Would like to see this getting merged asap. This prevents my app from having custom non-resizable window with mica backdrop.

@pomianowski pomianowski merged commit 3b3c5b7 into lepoco:development Sep 15, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants