AcrylicMenus is not compatible with WIN10 (build 19042.1526).

I run the app, it works (only desktop's context menu). After the app closed, the menu's colors does not restore back the original. I already tried to switch between themes, but it is not resolved. Even I rebooted PC. Please help me with a workaround or an update ASAP. Thanks.

.

While navigating/selecting items in a context menu using the up/down arrow keys, there is no indication of the currently selected item by means of a highlight or outline around that item (as Windows has by default).

Without AcrylicMenus (note the expected outline around the selected item, "Sort by"):

With AcrylicMenus:

The items are of course still usable by activation, just that the selection would be blind.

(This is the same for context menus in File Explorer.)

I am on Windows 11 Pro, Version 22H2, Build 22622.598.

I want to put them in the first box. How can I do it?

not sure if this is obvious or by design, but i'm not getting any functionality on windows 11 arm64 - surface pro x. Is there anything i can try or do to make it work?

как это удалить?

Hello, I am trying to uninstall AcrylicMenus so I can use TranslucentFlyouts. I installed AcrylicMenus about a year ago and I'm not sure where I extracted the release. Is there any simple way to disable or uninstall AcrylicMenus?

I have a question about switching to TranslucentFlouts

Now the latest versions of TranslucentFlyouts support everything that was missing

In the ReadMe, you had previously written:

For minimal performance impact, all settings are hardcoded
[...]
AcrylicMenus supports all Win32 applications, excluding legacy and custom (ownerdrawn) popup menus, however, currently, for maximum stability and avoiding incompatibilities,

Does AcrylicMenus still have better performance, better stability, less incompatibility, or ANY other advantages compared to TranslucentFlyouts?

Allow (via conifg) to set Mica on the menus

Just wondering if it's possible to change the color of the right click menu border instead of removing it for Windows 10. If it has to transition the same way, changing the color to a shade of gray may look less glaring and still improve the look of the menus.

When you run coodesker, the desktop context menu does not have an acrylic effect.

Honeyview enables preview in context menu, and the context menu becomes very white.

When the "Launch folder windows in a separate process" option is on, AcrylicMenus will hook only Explorer desktop. It also doesn't hook Explorer windows launched by another app such as Notepad++ via "open containing folder" shortcut despite having that option off.

Hi! Great tiny app! Just works and doesn't steal a lot of CPU/GPU resources or anything.
Just I want to know how to change transparency. We can modify this without recompiling it?

Popup menus with Acrylic do not respect theme bitmaps, but rather use a square highlight.

With AcrylicMenus:

Without:

Only shows up when the menu is opened on the desktop but not in explorer

Refer to the attached image for further details.

After removing the white border in Windows 10 Dark Theme, the border can be seen for a moment before disappearing. Is there any fix?

Is it possible to remove or change the color of the seperator lines in the context menu?
If possible please mention a way to do it.

Please add registry switch to toggle INJECT_EXPLORER_ONLY so I won't have to download IDE to recompile the thing or please include an optional DLL with this option pre-compiled.

If the transparency of SetWindowCompositionAttribute is increased, the defects of font rendering will be very obvious.

Is it possible to get the same font rendering as StartAllBack?

Could you add a feature that give´s the option to modify the RGB color of the Contextmenu ?

I want to add this program to the startup folder. But if I do this, I think I will see a big consle when I turn on my PC. That's very bad!!

Thanks for developing the good app.
Look beautiful on my PC.

I suggested the acrylic effect can be applied on every apps and with blue backgroud as shown on above picture.

The version of winsdk I am using is 22621 and I encountered the error when compiling: ambigous symbol, and when I commented MENUPARTSEX in ThemeHelper, the program compiled successfully.

so, conditional preprocess should be used for MENUPARTSEX:

	// Windows 11 22H2+
#if !defined NTDDI_WIN10_NI // SDK 10.0.22621.0
	enum MENUPARTSEX
	{
		MENU_POPUPITEMKBFOCUS = 26,
		MENU_POPUPITEM_FOCUSABLE = 27
	};
#endif