v2.0.0-beta.1

[ALTaleX531]

1. Unify and optimize the reading logic of the registry, the current CONFIG.md is not completely fit for this version.
2. Fix a lot of rendering issues.
3. Fix the issue that custom rendering sometines cannot work.
4. Add a experimental registry value: "EnableFluentAnimation" at TranslucentFlyouts\Menu, set it to 1 to activate.

---

This discussion was created from the release v2.0.0-beta.1.

[WiseTomCat]

Glad you are polising this tweak which is already my daily driver.
Noticed the rounded corners have changed to sharp corners in this new update by default.
How do we get the rounded corners?
Is this the value to be changed? there is nothing on my registry so I have to create a custom value
CornerType

DWORD (32-bit) value that controls the corner type

0: Keep the default, use small corners

1: Square corners

2: Large corners

3: Small corners

Only applicable to Windows 11

Also I tried the EnableFluentAnimation but I can understand it is not that smooth right now as it flashes the full menu size while animating. Does changing to DIrect-2d in registry make it smoother?

[ALTaleX531]

Actually I didn't change it to sharp corners in this new update by default which I think it was a bug, can you show me your OS build information? The CornerType value does control the corner of the popup menu but I think it is also affected by this bug...
About the EnableFluentAnimation, I wonder what it looks like in your OS, can you post a video of it?

[WiseTomCat]

The left is the new updated flyout and right one is the older which has rounded corner.

Also I am not able to replicate that animating issue i had recently as it is working well right now. It is although a bit unsettling the way it animates but here is the video

2023-08-06.18-54-46.mp4

[ALTaleX531]

Actually it use small round corners in the new release to respect default popup menu corners option, you can manually change it, it is not a bug.
I think the latest release has solved the animation issue.

[WiseTomCat]

I also think its not a bug. it could be the symbol file you used for this update from windows 10!