v3.0.0

[ALTaleX531]

New Registry Keys and Items

HKEY_CURRENT_USER\Software\TranslucentFlyouts\BlockList
HKEY_CURRENT_USER\Software\TranslucentFlyouts\DisabledList
HKEY_CURRENT_USER\Software\TranslucentFlyouts\EnableMiniDump (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\DarkMode_ThemeColorizationType (string)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\LightMode_ThemeColorizationType (string)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Menu\DisabledList
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Menu\EnableCompatibilityMode (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Menu\DarkMode_ThemeColorizationType (string)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Menu\LightMode_ThemeColorizationType (string)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\DropDown\Animation
HKEY_CURRENT_USER\Software\TranslucentFlyouts\DropDown\DisabledList
HKEY_CURRENT_USER\Software\TranslucentFlyouts\DropDown\EnableFluentAnimation (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\DisabledList
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\DarkMode_Color (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\LightMode_Color (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\MarginsType (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\Margins_cxLeftWidth (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\Margins_cxRightWidth (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\Margins_cyTopHeight (dword)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\Margins_cyBottomHeight (dword)

I don't have time to document each of these new features and registry items due to academic reasons, but you can ask what they do in Discussion and I'll respond later.
This version fixes almost all the bugs, please try it.

New Contributors

• @ddzzkunye made their first contribution in readme层级改进 #67

Full Changelog: v2.1.0...v3.0.0

---

This discussion was created from the release v3.0.0.

[Satanarious]

Does it also fix the problem where it somehow messes with vanguard, the anti-cheat in Valorant?

[ALTaleX531]

In my tests I can start Valorant without problems, they seem to have changed the anti-cheat algorithm, you can confirm this yourself.

[Satanarious]

If you get time, I would appreciate it if you documented the changes. Otherwise, I would require the following information to support TF v3.0:

• Values acceptable for all new keys
• What purpose does each key serve and how any acceptable value change the appearance or behaviour of TF

Though I tested nothing, I made the following speculations:

• I see you have BlockList and DisabledList, which I suppose accept process names as keys and 0 or 1 as DWORD values to signify blocked/disabled status. Let me know more about this.
• There is now an Animation key for DropDown. We currently have animation in the menu section in TFC. Is it similar to this or something else?
  
• We already have DarkModeBorderColor and DarkModeGradientColor and their light mode counterparts, what is DarkModeColor for in Tooltip? You only used DarkModeColor and LightModeColor in TF/Menu keys. Is this being used in favor of removing the former two?
  

Let me know if I need to remove anything from the previous build of TFC, like keys or something. And don't forget the first thing I asked.

[Satanarious]

Got it.

[ALTaleX531]

HKEY_CURRENT_USER\Software\TranslucentFlyouts\Menu\DarkMode_ThemeColorizationType (REG_MULTI_SZ)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Menu\LightMode_ThemeColorizationType (REG_MULTI_SZ)
...

Correction: it's REG_SZ not REG_MULTI_SZ.

[Satanarious]

I would also like to know the default value for each key.

Edit: By the above I mean, what keys need to be present to be considered and what default values are assumed in the absence of those keys?

[Satanarious]

HKEY_CURRENT_USER\Software\TranslucentFlyouts\DropDown\DarkMode_ThemeColorizationType (string)
HKEY_CURRENT_USER\Software\TranslucentFlyouts\DropDown\LightMode_ThemeColorizationType (string)

Do these exist for DropDown? Or you forget to mention them? Because there is an EnableThemeColorization key for DropDown.

[ALTaleX531]

All keys exist with corresponding default values.
EnableMiniDump -> 1
DarkMode_ThemeColorizationType | LightMode_ThemeColorizationType -> ImmersiveStartHoverBackground
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\DarkMode_Color -> 0xFFFFFFFF
HKEY_CURRENT_USER\Software\TranslucentFlyouts\Tooltip\LightMode_Color -> 0xFF1A1A1A
MarginsType -> 0
Margins_cxLeftWidth | Margins_cxRightWidth | Margins_cyTopHeight | Margins_cyBottomHeight -> 6

In fact, DarkMode_ThemeColorizationType and LightMode_ThemeColorizationType exist everywhere EnableThemeColorization exists, so I've omitted them to avoid taking up too much space.

[e-t-l]

Between releases v3.0.0 and v3.0.1, it seems like you sometimes include
TranslucentFlyouts.Win32.V3.x86.optional.rar with TFmain32.dll, and sometimes not. What determines whether or not the 32-bit version is included?

[ALTaleX531]

The x86 version wasn't ready when v3.0.0 was released, so it wasn't included.

[A-Basir]

There is no install_win32.bat for the TranslucentFlyouts.Win32.V3.x86.optional but there is a launch_win32.bat for that
But I have to manually open it after each reboot ( for now I added launch_win32.bat to startup )
Did you forget to add it or is there a reason for that? like compatibility issues?

[ALTaleX531]

I think I forgot to add it, thanks for the reminder. You can change the parameter of the command inside launch_win32.bat to /install to install it.

[A-Basir]

I checked the launch_win32.bat and actually the command is /install but somehow I need to start it every reboot

[Satanarious]

I am sorry to bother you again, but I forgot if you need a restart after altering the DisabledList or BlockList. Can you help?

Here's a peek into the new DisabledList UI 😁,

[ALTaleX531]

DisabledList takes effect immediately after the settings are changed, while BlockList requires them to restart for apps added later.

I think the button to enable/disable process items also needs to be added, other than that this UI has been a great surprise to me.

[Satanarious]

Up until now, I removed any value that had a default value. 0 for any item in DisabledList means that the value has no effect even if it is present in the key. But knowing that it takes effect immediately, a switch for enable/disable seems logical. I will make the required additions.

Thanks for the feedback.

[Satanarious]

These are the colors for each mentioned type, right? I'm doubtful because I don't know what these values do.

[ALTaleX531]

These colors are not fixed, they will adjust slightly with your theme colors so it is unlikely to preview them. These colors are often used in different parts of the UI, with darker colors indicating less important background surfaces. Important surfaces are highlighted with brighter and lighter colors. To be honest, these values come from disassembling Microsoft's system components, and I know no more about it than you do.

[Satanarious]

I think I understand now. So, should I not show the colors at all, and show only the values? How would the user understand the values though?

[ALTaleX531]

Of course, it's not completely impossible to preview, it's just that I think it's hard to implement on the python side. At the moment it looks like you can only show the values and tell the user that these are variants of the color, after all, almost no one knows what these values are actually used for.

[Satanarious]

I'm writing descriptions for the new values. I would like some more details on:

- DarkModeThemeColorizationType
- LightModeThemeColorizationType
- EnableCompatibilityMode

[ALTaleX531]

DarkMode_ThemeColorizationType and LightMode_ThemeColorizationType are used to indicate which variant of the current theme color to use, which are usually darker and lighter, and are used in various parts of the UI.
EnableCompatibilityMode will enable a v1-like rendering procedure for your vanilla menus, so symbols are no longer needed for that section, but the rendering will be performed slightly more slowly.