v0.10.0-beta.5

[Samuel12321]

Maintenance release to restart development

What's Changed

• Generated New Signing certificate
• updated .net to 9 preview
• fixed crash on launch
• integrated fixes from Requested Features - Personalisation #1217
• Updated Nuget Packages

• add GSMTC support status for feeluown by @mokurin000 in add GSMTC support status for feeluown #1261
• fix How-Tos link on README by @IsaacHatton in fix How-Tos link on README #1306

New Contributors

• @mokurin000 made their first contribution in add GSMTC support status for feeluown #1261
• @IsaacHatton made their first contribution in fix How-Tos link on README #1306

Full Changelog: v0.10.0-beta.4...v0.10.0-beta.5

Other:
Remember to install the certificate in the trusted root authority under "local machine". As this is a pre-release i haven't signed it via the MS Store.

---

This discussion was created from the release v0.10.0-beta.5.

[jh30uk]

Thank you.

[GibbyGibson1]

Can someone help me install this/ join your discord for more questions

[gamnull]

Is it possible to remove the gray border?

[Genz-RBX]

Thank god i found this, 0.9.3.0 on my pc(win11) was just showing invisible audio flyout

[vyrtuaPRO]

Even i install the certificate correcly windows return with error and ModernFlyouts doesnt show on superior bar. Any tips?

[GeorgeTheProgrammer01]

If anyone needs help with installation.

Run the certificate first, Install Certificate > Local Machine > "Place all certificates in the following store" Look for "Trusted People"

Then install the Modern Flyout

[yarkiv]

Hi. Thank you for this update. it works very well. But after scan my PC. My Antivirus delete somes files and warm me about malwares

after scan : dump:generic.dacic.3754.2f30bf4f

Warning on 0.10.5 exe : -> Gen:Variant.Lazy.631262

So I unistall it (so sad)

I tried to use the previous version (no AV warning with 0.10.4 exe) , but I can't install it despite cert. installation.

is it possible to push a clean version on MS Store ?

[MNLierman]

Hey, I just wanted to comment and say that, while I trust you, I believe that installing the certificate as a Trusted Root Authority is a very bad security practice. The proper place to install the certificate would be Trusted People. This allows someone with administrator permissions to install something they are aware of but without introducing massive security vulnerabilities by adding a Trusted CA Authority Certificate. The implications of this could be catistrophic. Like I said, I trust you, and I appreciate your work on this, but it would be much safer to recommend that everyone install the certificate in Trusted People which is a sort of supervised trusted certificate store.

[GeorgeTheProgrammer01]

I appreciate your input but I'm not one of the developers/contributors to this. I just commented on how I was able to install it on my machine.

[manstheram]

I actually would suggest you do not install this app for a while. I contributed a while back. The app is currently being rewritten by some guy, and will be updated eventually (hopefully). This beta version may have some issues with it and was only made as a response to the overwhelming amount of issues relating to outdated certificate problems. This version already has a lot of workarounds in it, without testing so much, so I would not suggest using it in its current state, at least for the moment being.

[MNLierman]

I appreciate your input but I'm not one of the developers/contributors to this. I just commented on how I was able to install it on my machine.

I thought I was replying to the Release. At least that's where my GitHub app shows me that I am commenting. The person who posted this release is suggesting to everyone to install the certificate as a Root CA Certificate which is incredibly bad security practice. It looks like you also commented about installing the certificate in Trusted People which is the correct thing to do. I would venture to Guess that a lot of people are unaware of how to properly install certificates and the best standard practices for doing so.

But anyways, my comment shows as a comment reply to the latest release.

Also, for me, the reason why I'm using this is because it's the only thing I've been able to find that has a good looking caps lock, insert lock OSD message. I like being aware of when these keys are turned on as I don't like having to retype things like passwords. Even if retyping something only takes a couple of seconds.

[komidawi]

@MNLierman Could you please tell what software did you try for OSD messages feature? Then just in a few words tell why you didn't like it.
AFAIK there's such a feature in Windows natively, also probably Dell and/or Asus have their apps capable of OSD (but probably at the same time being highly bloated).
Thanks.

[lomba481]

I installed the certificate as you suggested, but when I double-click the .exe file, nothing happens.

[lomba481]

Actually, now even the default Windows flyouts don’t show up.

[komidawi]

In my case simple restart fixes this problem.

In case you don't see anything in the tray, do the following:
Ctrl + Alt + Delete → Task Manager, Find Modern Flyouts, Right Click on it → End Task.
Wait until it disappears, wait a few seconds, run it again (e.g. from Windows Start Menu).
Check tray, Right Click → Settings, General → Default Flyout and set Windows default - then check if it works.
Then try again checking ModernFlyouts.
ModernFlyouts should now work properly.

Hope it helps!

[lomba481]

Unfortunately, my issue is different because ModernFlyouts doesn’t install at all. So, it doesn’t appear in Task Manager, and I can’t restart it as suggested. Do I need to click on the ModernFlyoutsHost_x64.exe file to install it? Do you have any other solutions I could try?