ModernFlyouts
ModernFlyouts copied to clipboard
ModernFlyouts-Community
ModernFlyouts does not replace the new Windows 11 flyouts
ModernFlyouts Version
0.9.3.0
Windows version
Windows 11 Insider Preview
OS build
22533.1001
Platform
x64
Area(s) with issue?
General
Steps to reproduce
- Make sure you're in the Dev ring (at the time of writing this)
- Update to the latest version of W11 (at the time of writing this, 22533.1001)
- If it isn't configured to start on startup, run ModernFlyouts
- Trigger any action that would trigger both the built-in flyout and ModernFlyous (e.g. change your volume or brightness)
✔️ Expected Behavior
The ModernFlyouts flyout replaces the built-in one.
❌ Actual Behavior
Both flyouts display:
Other Software
No response
Additional Context
I suspect that due to the completely new built-in flyout something (file locations?) that MF currently relies on/overwrites is no longer used?
Same here, this is probably related to the new rework of the flyout interface. Hopefully fixing this doesn't break support for older versions of Windows.
This happens on the beta branch too now since both branch merged on this update
Yup this is happening to me too in the new 22H2, just updated...
@yodaluca23 make sure to read the whole thread before replying. They're working on it for version 0.11.
Yup this is happening to me too in the new 22H2, just updated...
@yodaluca23 make sure to read the whole thread before replying. They're working on it for version 0.11`.
I saw, just didn't see anyone specifying that it did not work in the non-beta's... so I figured I'd reply...
I saw, just didn't see anyone specifying that it did not work in the non-beta's... so I figured I'd reply...
Makes sense. For your information the betas have very little difference from the final release. Just minor changes. For example, when I was using Windows 11 Beta before its initial release, the last beta from September 23rd ended up being the same exact build as the official release on October 5th.
Also a question for you, why do you put ellipses at the end of your comments? It could be misinterpreted as some sort of passive aggressive thing, though I don't think that's why you're using it
Since there's a lot of unnecessary spam in this thread from users who don't understand that the problem has already been acknowledged, to those who don't want their email bombarded, update your subscription settings for this issue to only notify you when the issue has been closed (click Customize) (also, please use @Ridoou's workaround from above if you can't wait):
This fork version of HideVolumeOSD seems to work more reliably than the original version for me on Windows 11, resuming from sleep doesn't reactivate windows 11 volume osd.
still happening, but this could be a temporary fix
I use HideVolumeOSD by Marcus Venturi to hide the W11 one
Another thought - I don't know how difficult it is to implement, but if removing the native Windows flyout is difficult, would having an option to disable just ModernFlyouts' volume slider but show any playback media be a temporary workaround?
would having an option to disable just ModernFlyouts' volume slider but show any playback media be a temporary workaround?
Yes this is exactly what I would like to be able to do too. Even if the ability to hide the new flyouts gets added, I would love if I could use the new windows volume flyouts but keep the media flyout that would only open when I pause/play the music
Considering the fact that the last update to this app was a year ago and there are over 200 open issues, I have to question whether any development is even being performed. I think this app has become abandonware.
I've submitted a pull-request that fixes this, so hopefully it's added soon.
