Skip to content

Add preview background in welcome page 2 #3277

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

Merged

Conversation

Jack251970
Copy link
Member

Add preview background in welcome page 2

There is Background="{Binding PreviewBackground}" in WelcomePage2.xaml, but I cannot find this in WelcomePage2.xaml.cs, so I believe this brush seems to have been left out.

Test

image

@Jack251970 Jack251970 added the bug Something isn't working label Feb 25, 2025
@Jack251970 Jack251970 enabled auto-merge February 25, 2025 05:52
Copy link

@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
Contributor

coderabbitai bot commented Feb 25, 2025

📝 Walkthrough

Walkthrough

This change adds a new public property, PreviewBackground, to the WelcomePage2 class. The property checks for a valid wallpaper using WallpaperPathRetrieval.GetWallpaperPath(). If a valid image file is found, it reads the file into a memory stream, creates a bitmap image with dimensions 800x600, and returns an ImageBrush set to stretch the image. If the wallpaper isn't available, it retrieves a fallback color via WallpaperPathRetrieval.GetWallpaperColor() and returns a SolidColorBrush. Additional using directives for System.IO and System.Windows.Media.Imaging were also added.

Changes

File Change Summary
Flow.Launcher/Resources/Pages/WelcomePage2.xaml.cs Added public property PreviewBackground. Implements wallpaper retrieval logic by checking file existence, creating a memory stream, initializing a 800x600 bitmap image, and selecting between an ImageBrush or SolidColorBrush based on availability. New using directives for System.IO and System.Windows.Media.Imaging were added.

Sequence Diagram(s)

sequenceDiagram
    participant UI as Client/UI
    participant WP2 as WelcomePage2
    participant Retrieval as WallpaperPathRetrieval

    UI->>WP2: Access PreviewBackground property
    WP2->>Retrieval: GetWallpaperPath()
    alt Wallpaper exists and file is valid
        Retrieval-->>WP2: Return wallpaper path
        WP2->>WP2: Check file existence
        WP2->>WP2: Read file into MemoryStream
        WP2->>WP2: Initialize BitmapImage (800x600)
        WP2-->>UI: Return ImageBrush (stretched)
    else Wallpaper not available
        Retrieval-->>WP2: No valid wallpaper
        WP2->>Retrieval: GetWallpaperColor()
        Retrieval-->>WP2: Return fallback color
        WP2-->>UI: Return SolidColorBrush
    end
Loading

Suggested reviewers

  • jjw24

Poem

Oh, what a scene in the code carrot patch,
I hopped through logic without a scratch.
A wallpaper found or not, a choice so bright,
My memory streams dance in the moonlight.
With colors fallback like a tender, soft touch,
A rabbit’s code hop, oh, it means so much!
🐇🥕

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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: 1

🧹 Nitpick comments (2)
Flow.Launcher/Resources/Pages/WelcomePage2.xaml.cs (2)

34-54: Exception handling needed for image loading.

The current implementation doesn't handle exceptions that could occur during image loading. If the wallpaper file exists but is corrupted or not a valid image, this could throw an unhandled exception.

Consider adding try-catch blocks:

  public Brush PreviewBackground
  {
      get
      {
          var wallpaper = WallpaperPathRetrieval.GetWallpaperPath();
          if (wallpaper is not null && File.Exists(wallpaper))
          {
+             try
+             {
                  var memStream = new MemoryStream(File.ReadAllBytes(wallpaper));
                  var bitmap = new BitmapImage();
                  bitmap.BeginInit();
                  bitmap.StreamSource = memStream;
                  bitmap.DecodePixelWidth = 800;
                  bitmap.DecodePixelHeight = 600;
                  bitmap.EndInit();
                  return new ImageBrush(bitmap) { Stretch = Stretch.UniformToFill };
+             }
+             catch (Exception ex)
+             {
+                 // Log the exception
+                 System.Diagnostics.Debug.WriteLine($"Error loading wallpaper: {ex.Message}");
+                 // Fall through to the fallback color
+             }
          }

          var wallpaperColor = WallpaperPathRetrieval.GetWallpaperColor();
          return new SolidColorBrush(wallpaperColor);
      }
  }

45-46: Consider preserving image aspect ratio.

The current implementation uses fixed dimensions (800x600) which might distort some wallpapers. While the UniformToFill stretch mode helps, it would be better to maintain the aspect ratio during decoding.

Consider setting only one dimension (e.g., width) and letting the height scale proportionally:

- bitmap.DecodePixelWidth = 800;
- bitmap.DecodePixelHeight = 600;
+ bitmap.DecodePixelWidth = 800; // Set only the 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 022cad0 and 928ca47.

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

8-10: Appropriate using directives added.

The additional using directives for System.IO, System.Windows.Media.Imaging, and System.Windows.Media are correctly included to support the new property implementation.

@Jack251970 Jack251970 requested a review from onesounds February 25, 2025 05:59
@Jack251970 Jack251970 merged commit 9aadc3a into Flow-Launcher:dev Feb 25, 2025
7 checks passed
@jjw24 jjw24 added this to the 1.20.0 milestone Feb 25, 2025
Copy link

gitstream-cm bot commented Feb 25, 2025

🥷 Code experts: taooceros

Jack251970 has most 👩‍💻 activity in the files.
Jack251970, taooceros have most 🧠 knowledge in the files.

See details

Flow.Launcher/Resources/Pages/WelcomePage2.xaml.cs

Activity based on git-commit:

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

Knowledge based on git-blame:
Jack251970: 45%
taooceros: 21%

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

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.

3 participants