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 main window resize border thickness issue #3232

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

Conversation

Jack251970
Copy link
Contributor

Issue

Because adding drop shadow effect will change the margin of the window border, we need to update the resize thickness of the window chrome to correct set the resize border. Otherwise, scrollbar selection is unable to work because resize area override it.

Tested Video:

2025-02-07.20-22-33.mp4

@prlabeler prlabeler bot added the bug Something isn't working label Feb 7, 2025
Copy link

github-actions bot commented Feb 7, 2025

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

❌ Errors Count
❌ forbidden-pattern 22
⚠️ ignored-expect-variant 1
⚠️ non-alpha-in-dictionary 19

See ❌ Event descriptions for more information.

If the flagged items are 🤯 false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

Copy link

gitstream-cm bot commented Feb 7, 2025

🥷 Code experts: onesounds

Jack251970 has most 👩‍💻 activity in the files.
onesounds has most 🧠 knowledge in the files.

See details

Flow.Launcher.Core/Resource/Theme.cs

Activity based on git-commit:

Jack251970
FEB
JAN
DEC 2 additions & 96 deletions
NOV 2 additions & 2 deletions
OCT
SEP

Knowledge based on git-blame:
onesounds: 7%

Flow.Launcher/MainWindow.xaml

Activity based on git-commit:

Jack251970
FEB
JAN
DEC
NOV 1 additions & 1 deletions
OCT
SEP

Knowledge based on git-blame:
onesounds: 91%

To learn more about /:\ gitStream - Visit our Docs

Copy link

gitstream-cm bot commented Feb 7, 2025

Be a legend 🏆 by adding a before and after screenshot of the changes you made, especially if they are around UI/UX.

@Jack251970 Jack251970 changed the title Fix main window resize boarder thickness issue Fix main window resize border thickness issue Feb 7, 2025
Copy link
Contributor

coderabbitai bot commented Feb 7, 2025

📝 Walkthrough

Walkthrough

The changes update how the application handles window chrome styling. In the Theme class, a new using directive is added and the AddDropShadowEffectToCurrentTheme method now uses a variable for margin definition and calls a new SetResizeBoarderThickness method, which computes the resize border thickness based on a provided margin. The RemoveDropShadowEffectFromCurrentTheme method similarly calls this new method with null to reset the border thickness. Additionally, the MainWindow.xaml file is modified by removing the ResizeBorderThickness attribute from the WindowChrome element.

Changes

File(s) Change Summary
Flow.Launcher…Theme.cs Added using directive for System.Windows.Shell; updated AddDropShadowEffectToCurrentTheme to use a variable margin and call SetResizeBoarderThickness; added new private static method SetResizeBoarderThickness to adjust window resize border thickness; updated RemoveDropShadowEffectFromCurrentTheme to reset border thickness.
Flow.Launcher…MainWindow.xaml Removed the ResizeBorderThickness attribute from the WindowChrome element, simplifying the window chrome configuration.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant T as Theme
    participant W as WindowChrome

    U->>T: Invoke AddDropShadowEffectToCurrentTheme
    T->>T: Define 'margin' (Thickness)
    T->>T: Call SetResizeBoarderThickness(margin)
    T->>W: Update ResizeBorderThickness property
Loading
sequenceDiagram
    participant U as User
    participant T as Theme
    participant W as WindowChrome

    U->>T: Invoke RemoveDropShadowEffectFromCurrentTheme
    T->>T: Call SetResizeBoarderThickness(null)
    T->>W: Reset ResizeBorderThickness to system default
Loading

Suggested reviewers

  • jjw24

Poem

Hop along the code trail, swift and bright,
I’m a rabbit dancing in the night.
Margins and borders now updated with grace,
A drop shadow magic on every interface.
Bugs beware, for improvements now delight!
🐇💻 Keep on hopping to new heights!


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
Flow.Launcher.Core/Resource/Theme.cs (1)

366-389: Fix typo in method name: "Boarder" should be "Border".

The implementation correctly handles the resize border thickness calculation, but there's a typo in the method name.

Apply this diff to fix the typo:

-        private static void SetResizeBoarderThickness(Thickness? effectMargin)
+        private static void SetResizeBorderThickness(Thickness? effectMargin)

Don't forget to update the method calls at lines 318 and 361 as well:

-                SetResizeBoarderThickness(margin);
+                SetResizeBorderThickness(margin);
-            SetResizeBoarderThickness(null);
+            SetResizeBorderThickness(null);
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 38eb07a and 1a39af3.

📒 Files selected for processing (2)
  • Flow.Launcher.Core/Resource/Theme.cs (4 hunks)
  • Flow.Launcher/MainWindow.xaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: gitStream.cm
  • GitHub Check: gitStream.cm
🔇 Additional comments (4)
Flow.Launcher.Core/Resource/Theme.cs (3)

14-14: LGTM!

The added using directive is correctly placed and necessary for accessing the WindowChrome class.


310-318: LGTM! The changes improve readability and fix the resize border issue.

The margin variable extraction and the call to SetResizeBoarderThickness are well-placed to ensure the resize border thickness is correctly set when adding the drop shadow effect.


361-361: LGTM! The changes ensure proper cleanup of resize border thickness.

The call to SetResizeBoarderThickness(null) correctly resets the resize border thickness when removing the drop shadow effect.

Flow.Launcher/MainWindow.xaml (1)

40-40: LGTM! The removal of ResizeBorderThickness is correct.

The resize border thickness is now managed dynamically by the Theme class through the SetResizeBorderThickness method, making this static attribute unnecessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant