Alpha value bug when set to 0

[Lukoning]

I had frequently changed config in TranslucentFlyoutsConfig before the error
Trigger process: simply double-click TranslucentFlyoutsConfig.exe

I tried the following:
Restart TranslucentFlyoutsConfig
Restart TranslucentFlyouts V2
Sign out & sign in Windows
Restart Windows
Replace TranslucentFlyoutsConfig with V1.4.2 Release from GitHub
Replace TranslucentFlyoutsConfig with V1.4.0 Release from GitHub

Unfortunately, although TranslucentFlyouts V2 is working correctly, TranslucentFlyoutsConfig is still... :(

[Satanarious]

Did you, by any chance, edit the registry or the JSON files containing the user data manually?

[Lukoning]

Did you, by any chance, edit the registry or the JSON files containing the user data manually?

I haven't touched any registry or JSON except zh-cn.json and hi-in.json

[Satanarious]

Okay, I will look into this. It's probably something that I overlooked while fixing the colours.
Can you share your Assets/db/user_settings.json ?

[Lukoning]

This JSON file was probably replaced when I tried to replace files from GitHub.

If needed:
user_settings.json

[Satanarious]

Thank you for providing the file. I have identified the problem; It will be fixed soon.

[Satanarious]

For the time being, you can get it fixed by following the below-mentioned steps:

• Open the 'Registry Editor' by searching for it in the start menu.
• In the address bar, type HKEY_CURRENT_USER\SOFTWARE\TranslucentFlyouts and press enter.
• Delete the values DarkModeBorderColor and LightModeBorderColor
• Run 'TranslucentFlyoutsConfig.exe' again.

You probably set the alpha value for those to 0, which caused this bug and, hence, the error.
Let me know if this fixes it.

[Lukoning]

For the time being, you can get it fixed by following the below-mentioned steps:

• Open the 'Registry Editor' by searching for it in the start menu.
• In the address bar, type HKEY_CURRENT_USER\SOFTWARE\TranslucentFlyouts and press enter.
• Delete the values DarkModeBorderColor and LightModeBorderColor
• Run 'TranslucentFlyoutsConfig.exe' again.

You probably set the alpha value for those to 0, which caused this bug and, hence, the error. Let me know if this fixes it.

It's OK: