Add WindhawkModSettings for frosted-acrylic-sheet

[EvanYFWong]

Summary
Add valid WindhawkModSettings block and embed style resources so CI validation passes and users can configure the mod.

Mod authorship

• Author: Evan
• GitHub: https://github.com/EvanYFWong
• License: MIT

Changes

• Add WindhawkModSettings block to mods/frosted-acrylic-sheet.wh.cpp exposing:
  • enableAcrylic (bool, default: true)
  • blurOpacity (number, default: 0.15, range 0.0–1.0)
  • taskbarFrameWidth (number, default: 1410)
  • taskbarHeight (number, default: 60)
  • iconSize (number, default: 40)
• Keep embedded README and style constants in mods/frosted-acrylic-sheet.wh.cpp (styles sourced from EvanYFWong/FrostedAcrylicSheet).

Reason / Notes

CI validation previously failed because the WindhawkModSettings block was empty. This PR provides a valid YAML settings block so:

• The repository validation no longer treats the settings block as an unexpected/empty marker.
• Users can configure the mod from Windhawk's UI.
  This mod is a configuration wrapper for the existing Windows 11 Taskbar Styler; it does not replace that mod — it supplies ready-to-use style constants and control styles.

Testing

• Verified on Windows 11 23H2 and 24H2.
• Works with both light and dark system themes (adapts via theme resources).
• Preview image: https://raw.githubusercontent.com/EvanYFWong/FrostedAcrylicSheet/main/screenshot.png

Key files

• mods/frosted-acrylic-sheet.wh.cpp — mod definition, README, settings block and embedded styles

Checklist

• I kept the required "## Mod authorship" section from the PR template.
• Mod ID is unique (frosted-acrylic-sheet)
• @github matches my GitHub account (EvanYFWong)
• @include explorer.exe is present
• License is set to MIT
• README is clear and includes installation steps

[EvanYFWong]

Hi @ramensoftware maintainers, this PR fixes CI validation by adding a valid WindhawkModSettings block (small change, checks passed). Could someone please review and merge when convenient?
Thank you!

[m417z]

Submission review

Note: This review was done by Claude, and then refined manually. Due to the amount of submissions, doing a fully manual review for each pull request is no longer feasible. Thank you for understanding.

Please address the following issues. The items in the collapsed sections are optional, so it's your call whether to address them.

---

The core problem is that this mod does not do anything, and its actual purpose is already served by an existing mod.

1. The mod has no functional code — it's a no-op. There are no hooks, no settings reads, and the two embedded strings (g_styleConstants at line 90 and g_controlStyles at line 102) are never referenced anywhere in the code. All five lifecycle callbacks (Wh_ModInit, Wh_ModAfterInit, Wh_ModSettingsChanged, Wh_ModBeforeUninit, Wh_ModUninit) only call Wh_Log. When a user enables this mod, it has zero effect on the taskbar. The visual result described in the README is produced entirely by the user manually pasting text into a different mod ("Windows 11 Taskbar Styler") — this mod contributes nothing at runtime. A Windhawk mod must actually do something when enabled; a wrapper that only carries instructions and unused string literals isn't a mod.

2. This is a theme for "Windows 11 Taskbar Styler," not a standalone mod. The existing windows-11-taskbar-styler mod is explicitly "Customize the taskbar with themes contributed by others or create your own." The frosted-acrylic look is precisely such a theme — and your own README already directs users to paste it into that mod. The right home for it is the Windows 11 taskbar styling guide / theme collection (the same channel your README points at for the start-menu equivalent), not a duplicate no-op mod in the catalog. Merging this as a separate mod fragments the catalog and delivers no functionality. Please contribute it as a theme instead of a mod.

3. Every declared setting is dead. enableAcrylic, blurOpacity, taskbarFrameWidth, taskbarHeight, and iconSize are declared in the ==WindhawkModSettings== block but never read anywhere (no Wh_GetIntSetting/Wh_GetStringSetting calls exist). Changing any of them does nothing. This is a direct consequence of #1 — the PR was made to "add a valid settings block so CI passes," but a settings block that no code reads is not meaningful configuration.

4. Non-English text in @description. The description ends with 磨砂亚克力板任务栏样式 appended to the English text. User-facing strings default to English; provide the Chinese variant via metadata localization (// @description:zh-CN ...) rather than mixing both languages in the primary field.

Optional improvements

Minor polish — and largely moot given the mod needs a functional rewrite (or conversion to a theme) anyway.

• @compilerOptions -lruntimeobject is unused. The mod links runtimeobject but uses no WinRT/Ro* APIs (it includes only <windows.h> and <windhawk_utils.h>). Drop it.
• $min / $max / $step are not recognized settings keys. No mod in the repo uses them and Windhawk doesn't act on them, so the range/step you specified for blurOpacity has no effect. Relatedly, blurOpacity: 0.15 is a fractional default, but Windhawk numeric settings are integers (read via Wh_GetIntSetting), so a value like 0.15 can't be read back as a float.
• The five log-only lifecycle callbacks are just placeholders; they'd disappear in a real implementation or when the styles move to a theme.

Functionality notes

Observations about the style content itself — relevant if/when it's contributed as a theme.

• The styles hard-code absolute pixel values — TaskbarFrameWidth=1410, SystemTray Width=270, and especially Margin=390,0,574,12 on the input-switcher — which assume a specific screen width and DPI. On other resolutions, multi-monitor setups, or non-100% scaling, the centered frame and these margins won't line up. Worth documenting the target resolution, or deriving widths adaptively (your README already mentions a "Set to 0 to use adaptive width" mode).

[EvanYFWong]

Apologies for taking up your time. My original intent was to contribute this code as a theme/style for the existing Windows 11 Taskbar Styler mod. This is my first time using the repository, so I’m not yet familiar with where theme files should be placed. Could you please advise which folder I should submit it to so it will be treated as a Windows 11 Taskbar Styler theme? I will make the necessary corrections promptly. Thank you for your guidance.

…

________________________________ 发件人: Michael Maltsev ***@***.***> 发送时间: 2026年7月13日 15:36 收件人: ramensoftware/windhawk-mods ***@***.***> 抄送: Evan ***@***.***>; Author ***@***.***> 主题: Re: [ramensoftware/windhawk-mods] Add WindhawkModSettings for frosted-acrylic-sheet (PR #4768) [https://avatars.githubusercontent.com/u/4129781?s=20&v=4]m417z left a comment (ramensoftware/windhawk-mods#4768)<#4768 (comment)> Submission review Note: This review was done by Claude, and then refined manually. Due to the amount of submissions, doing a fully manual review for each pull request is no longer feasible. Thank you for understanding. Please address the following issues. The items in the collapsed sections are optional, so it's your call whether to address them.

________________________________ The core problem is that this mod does not do anything, and its actual purpose is already served by an existing mod. 1. The mod has no functional code ― it's a no-op. There are no hooks, no settings reads, and the two embedded strings (g_styleConstants at line 90 and g_controlStyles at line 102) are never referenced anywhere in the code. All five lifecycle callbacks (Wh_ModInit, Wh_ModAfterInit, Wh_ModSettingsChanged, Wh_ModBeforeUninit, Wh_ModUninit) only call Wh_Log. When a user enables this mod, it has zero effect on the taskbar. The visual result described in the README is produced entirely by the user manually pasting text into a different mod ("Windows 11 Taskbar Styler") ― this mod contributes nothing at runtime. A Windhawk mod must actually do something when enabled; a wrapper that only carries instructions and unused string literals isn't a mod. 2. This is a theme for "Windows 11 Taskbar Styler," not a standalone mod. The existing windows-11-taskbar-styler<https://github.com/ramensoftware/windhawk-mods/blob/main/mods/windows-11-taskbar-styler.wh.cpp> mod is explicitly "Customize the taskbar with themes contributed by others or create your own." The frosted-acrylic look is precisely such a theme ― and your own README already directs users to paste it into that mod. The right home for it is the Windows 11 taskbar styling guide / theme collection (the same channel your README points at for the start-menu equivalent<https://github.com/ramensoftware/windows-11-start-menu-styling-guide>), not a duplicate no-op mod in the catalog. Merging this as a separate mod fragments the catalog and delivers no functionality. Please contribute it as a theme instead of a mod. 3. Every declared setting is dead. enableAcrylic, blurOpacity, taskbarFrameWidth, taskbarHeight, and iconSize are declared in the ==WindhawkModSettings== block but never read anywhere (no Wh_GetIntSetting/Wh_GetStringSetting calls exist). Changing any of them does nothing. This is a direct consequence of #1<#1> ― the PR was made to "add a valid settings block so CI passes," but a settings block that no code reads is not meaningful configuration. 4. Non-English text in @description. The description ends with 磨砂亚克力板任务栏样式 appended to the English text. User-facing strings default to English; provide the Chinese variant via metadata localization (// @description:zh-CN ...) rather than mixing both languages in the primary field. Optional improvements Minor polish ― and largely moot given the mod needs a functional rewrite (or conversion to a theme) anyway. * @compilerOptions -lruntimeobject is unused. The mod links runtimeobject but uses no WinRT/Ro* APIs (it includes only <windows.h> and <windhawk_utils.h>). Drop it. * $min / $max / $step are not recognized settings keys. No mod in the repo uses them and Windhawk doesn't act on them, so the range/step you specified for blurOpacity has no effect. Relatedly, blurOpacity: 0.15 is a fractional default, but Windhawk numeric settings are integers (read via Wh_GetIntSetting), so a value like 0.15 can't be read back as a float. * The five log-only lifecycle callbacks are just placeholders; they'd disappear in a real implementation or when the styles move to a theme. Functionality notes Observations about the style content itself ― relevant if/when it's contributed as a theme. * The styles hard-code absolute pixel values ― TaskbarFrameWidth=1410, SystemTray Width=270, and especially Margin=390,0,574,12 on the input-switcher ― which assume a specific screen width and DPI. On other resolutions, multi-monitor setups, or non-100% scaling, the centered frame and these margins won't line up. Worth documenting the target resolution, or deriving widths adaptively (your README already mentions a "Set to 0 to use adaptive width" mode). ― Reply to this email directly, view it on GitHub<#4768?email_source=notifications&email_token=CEPKOADZ5NXS32R73FUTWVL5ESGOPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVGU2TIOBRHE3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4955548196>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CEPKOAF24N4WXJYO6F5UGBD5ESGOPAVCNFSNUABFKJSXA33TNF2G64TZHM2DIOBSGYZTAMZYHNEXG43VMU5TIOBWHE4DONRQGQ22C5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/CEPKOAFB4YEZ6MXL356SG5D5ESGOPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVGU2TIOBRHE3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android<https://github.com/notifications/mobile/android/CEPKOABVWFVTOHYH6PXDFVD5ESGOPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVGU2TIOBRHE3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[m417z]

Taskbar themes can be submitted here:
https://github.com/ramensoftware/windows-11-taskbar-styling-guide/tree/main/Themes

[EvanYFWong]

Thank you very much And I'll solve the problem of tyles hard-code absolute pixel values

…

________________________________ 发件人: Michael Maltsev ***@***.***> 发送时间: 2026年7月13日 17:28 收件人: ramensoftware/windhawk-mods ***@***.***> 抄送: Evan ***@***.***>; Author ***@***.***> 主题: Re: [ramensoftware/windhawk-mods] Add WindhawkModSettings for frosted-acrylic-sheet (PR #4768) [https://avatars.githubusercontent.com/u/4129781?s=20&v=4]m417z left a comment (ramensoftware/windhawk-mods#4768)<#4768 (comment)> Taskbar themes can be submitted here: https://github.com/ramensoftware/windows-11-taskbar-styling-guide/tree/main/Themes ― Reply to this email directly, view it on GitHub<#4768?email_source=notifications&email_token=CEPKOABWUI36V2Z44A7F54L5ESTUTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVGY2DMNJXHEZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4956465792>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CEPKOAHK37J7E2NH3NXJU4L5ESTUTAVCNFSNUABFKJSXA33TNF2G64TZHM2DIOBSGYZTAMZYHNEXG43VMU5TIOBWHE4DONRQGQ22C5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/CEPKOAACXQEBO5RNMOGNZ5L5ESTUTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVGY2DMNJXHEZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android<https://github.com/notifications/mobile/android/CEPKOAAKWWBKHFJV4XDSLDD5ESTUTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVGY2DMNJXHEZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>