BUG: Theme blur exceeds window with rounded corners.

[abidanBrito]

Checks

• [X] I have checked that this issue has not already been reported.

• [x] I am using the latest version of Flow Launcher.

Problem Description

When enabling blur on a theme with rounded corners, the blurred backdrop doesn't seem to round the corners, exceeding the boundaries of the window.

To Reproduce

1. Enable blur for your theme.

<system:Boolean x:Key="ThemeBlurEnabled">True</system:Boolean>

2. Add rounded corners. Here's the relevant snippet from my theme:

<Style
    x:Key="WindowBorderStyle"
    BasedOn="{StaticResource BaseWindowBorderStyle}"
    TargetType="{x:Type Border}">
    <Setter Property="CornerRadius" Value="10" />
    <Setter Property="BorderThickness" Value="0" />
    <Setter Property="BorderBrush" Value="Transparent" />
    <Setter Property="Background">
        <Setter.Value>
            <SolidColorBrush Opacity="0.6" Color="Black" />
        </Setter.Value>
    </Setter>
</Style>

Screenshots

Flow Launcher Version

1.16.2

Windows Build Number

10.0.22621.2283

Error Log

No relevant information within logs.

[deefrawley]

Seems relaated to #2298

[github-actions[bot]]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[flooxo]

I had a look at the bug and I think it is not related to the implementation in FlowLauncher, but to the Windows Presentation Foundation (WPF) framework, which does not support this feature. There is also an issue on this topic in the repo from which the blur is used. The current implementation does not support a blurred window with rounded corners.

I have tried to use the newer acrylic blur instead of the currently used aero blur, but logically this only changes the appearance and does not bring any new features.

While researching I also came across this post on Stackoverflow which might be helpful as it uses DwmEnableBlurBehindWindow and uses shapes to define which areas should be blurred and the solution should be compatible with WPF. Unfortunately this is beyond my abilities to implement it.

Nevertheless, I wanted to share my findings with you, as they might be helpful or let me know if I'm wrong :)

[deefrawley]

Please update to the latest version and if the issue persists we can reopen. Thanks

[flooxo]

I still have the issue with 1.18.0

[Foozey]

Can confirm this issue still exists in 1.18.0, would love to see a workaround!