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

Dynamically change mini-window window controls alignment based on window position #125

Merged
merged 1 commit into from
Feb 7, 2025

Conversation

justinshannon
Copy link
Contributor

@justinshannon justinshannon commented Feb 7, 2025

Summary by CodeRabbit

  • New Features
    • Enhanced window behavior by dynamically adjusting the alignment of control elements based on the window’s position relative to screen boundaries.
    • Improved UI configuration for streamlined interaction when the window is partially off-screen.

Copy link
Contributor

coderabbitai bot commented Feb 7, 2025

Walkthrough

This update assigns a Name ("WindowControls") to the StackPanel in CompactWindow.axaml for easier reference. Additionally, CompactWindow.axaml.cs now imports System.Linq and Avalonia.Layout and enhances the OnPositionChanged method. This method computes an aggregated bounding rectangle based on all screens and adjusts the HorizontalAlignment of WindowControls based on whether the window is partially off-screen.

Changes

File(s) Change Summary
vATIS.Desktop/Ui/Windows/CompactWindow.axaml Added Name="WindowControls" to the StackPanel element.
vATIS.Desktop/Ui/Windows/CompactWindow.axaml.cs Imported System.Linq and Avalonia.Layout; extended OnPositionChanged to compute screen bounds and update WindowControls' HorizontalAlignment accordingly.

Sequence Diagram(s)

sequenceDiagram
    participant User as User
    participant Window as CompactWindow
    participant Method as OnPositionChanged
    participant Display as ScreenManager
    participant Controls as WindowControls

    User->>Window: Moves window
    Window->>Method: Trigger OnPositionChanged
    Method->>Display: Aggregate working areas
    Display-->>Method: Return bounding rectangle
    Method->>Window: Check window boundaries
    alt Window partially off-screen
        Method->>Controls: Update HorizontalAlignment (Left/Right)
    else Window fully visible
        Method-->>Controls: No alignment change
    end
Loading

Poem

Hoppin' through the code with a joyful beat,
I found new names where old ones would meet.
With LINQ and logic, screens align so bright,
A rabbit cheers for changes done just right!
Keep on coding, day and night!


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.

@justinshannon justinshannon changed the title Dynamically change mini-window window controls based on window position Dynamically change mini-window window controls alignment based on window position Feb 7, 2025
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 (2)
vATIS.Desktop/Ui/Windows/CompactWindow.axaml.cs (2)

73-97: Add null check for WindowControls.

The implementation looks good! However, consider adding a null check before accessing WindowControls to prevent potential NullReferenceException.

-        if (isRightOffScreen)
+        if (WindowControls != null)
         {
-            WindowControls.HorizontalAlignment = HorizontalAlignment.Left;
-        }
-        else if (isRightFullyVisible)
-        {
-            WindowControls.HorizontalAlignment = HorizontalAlignment.Right;
+            if (isRightOffScreen)
+            {
+                WindowControls.HorizontalAlignment = HorizontalAlignment.Left;
+            }
+            else if (isRightFullyVisible)
+            {
+                WindowControls.HorizontalAlignment = HorizontalAlignment.Right;
+            }
         }

74-81: Consider extracting screen bounds calculation.

The screen bounds calculation logic could be moved to a separate method for better maintainability and reusability.

+    private PixelRect GetTotalScreenBounds()
+    {
+        return Screens.All
+            .Select(s => s.WorkingArea)
+            .Aggregate((acc, next) => acc.Union(next));
+    }
+
     private void OnPositionChanged(object? sender, PixelPointEventArgs e)
     {
         if (DataContext is CompactWindowViewModel model)
         {
             model.UpdatePosition(this);
         }
 
-        // Get the bounding rectangle of all screens combined
-        var totalScreenBounds = Screens.All
-            .Select(s => s.WorkingArea)
-            .Aggregate((acc, next) => acc.Union(next));
+        var totalScreenBounds = GetTotalScreenBounds();
 
         var totalLeft = totalScreenBounds.X;
         var totalRight = totalScreenBounds.X + totalScreenBounds.Width;
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0527dae and 89f7cdf.

📒 Files selected for processing (2)
  • vATIS.Desktop/Ui/Windows/CompactWindow.axaml (1 hunks)
  • vATIS.Desktop/Ui/Windows/CompactWindow.axaml.cs (2 hunks)
✅ Files skipped from review due to trivial changes (1)
  • vATIS.Desktop/Ui/Windows/CompactWindow.axaml
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: build (macos-latest)
  • GitHub Check: Analyze (cpp)
  • GitHub Check: build (windows-latest)
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: Analyze (csharp)
  • GitHub Check: Analyze (cpp)
  • GitHub Check: Analyze (csharp)
🔇 Additional comments (1)
vATIS.Desktop/Ui/Windows/CompactWindow.axaml.cs (1)

7-7: LGTM! Required imports added for new functionality.

The new imports support LINQ operations for screen bounds calculation and HorizontalAlignment for window controls positioning.

Also applies to: 12-12

@justinshannon justinshannon added this pull request to the merge queue Feb 7, 2025
Merged via the queue into main with commit 4fb353e Feb 7, 2025
9 checks passed
@justinshannon justinshannon deleted the feat/mini-window-controls-dynamic-alignment branch February 7, 2025 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant