Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Ability to replace the tray volume flyout #103

Open
WindowsFanBoi opened this issue Oct 12, 2020 · 5 comments
Open

Feature Request: Ability to replace the tray volume flyout #103

WindowsFanBoi opened this issue Oct 12, 2020 · 5 comments
Assignees
Labels
Enhancement New feature or request
Milestone

Comments

@WindowsFanBoi
Copy link

WindowsFanBoi commented Oct 12, 2020

I understand this is out of the scope for this app.

You aim to replace the default metro themed flyouts with fluent design based one.

But the name "ModernFlyouts" suggest that this can replace any flyout.

So, my request is to

  • Add the ability to select and change volumes of connected audio devices (Such a functionality could be seen in the tray volume flyout which is triggered by clicking the volume tray icon),

  • Ability to hook to the tray volume icon and replace the tray volume flyout.


Tray Volume Flyout

See we should also replace this flyout

The audio device selector could be optional while the normal flyout (due to the extra height it requires) is shown. But it should be mandatory while replacing the volume tray flyout.

I hope you can somehow add this ability 😄.

Another suggestion, as you may have a doubt by now:

Q: What would happen when the flyout is triggered by the tray volume icon and is shown near the tray and the ordinary flyout (such as audio/brightness/lockkeys/airplane mode) is triggered?

Should ModernFlyouts move there or Should there be another flyout?

A: When the triggered action is audio (both volume keys & media keys), nothing should happen i.e. the tray volume icon triggered flyout should stay open where it is. But when the action is other than audio, the flyout should be closed there and re-emerge to the position it should be (user defined or automatic).

This app has GSMTC support which the in-built tray volume flyout and EarTrumpet doesn't seem to. If you did implement this, we can consider this app as a replacement for the tray volume flyout and even EarTrumpet upto a level.

I see @ShankarBUS's proposal got rejected by the EarTrumpet's maintainers.

File-New-Project/EarTrumpet#475

If they don't plan adding GSMTC support, why not you extend your app to do it?

Thanks for creating this wonderful app 🤗.

Additional Infos:
This app has the most requested feature of many users i.e. ability to hide, fluent & so on...

https://twitter.com/RudyHuyn/status/1149840574196797440
https://twitter.com/mehedih_/status/1149638646242299904

Source: From an issue on PowerToys submitted by @Poopooracoocoo

MS finally seemed to take an action regarding this

Ref:

https://news.softpedia.com/news/microsoft-is-updating-the-windows-10-volume-flyout-with-new-features-523729.shtml

https://mspoweruser.com/windows-10-might-finally-get-modern-volume-flyout/

But it's far far from what this app does in functionality and doesn't look good IMO. Also it's MS after all 😂😂😂, there will be no way for proposals or bug report (except shhh... don't even talk about Feedback Hub). It took them 5 years roughly to do this. And the reference articles seems to be posted 6 months ago. It won't be available till at least 21H2.

This will be the right opportunity for you to shine.

@ShankarBUS
Copy link
Member

This would require much more work. I'll do my best.

@Poopooracoocoo
Copy link
Contributor

To add to your last point, Shankar has done a much better job than Microsoft probably ever could and he really listens to us.

@luximus-hunter
Copy link

This issue triggers the issue to weather or not to replace the battery and/or network flyout as well. they are flyouts after all

@ShankarBUS
Copy link
Member

Well @FireCubeStudios is working on the battery flyout. Others will be added in the future 😉.

@parthmawai
Copy link

parthmawai commented Apr 15, 2021

@ShankarBUS
I would suggest that you should not invest to much in design as we don't know exactly what design language 21H2 will follow, incorrect assumption could create odd appearances. It would be better to have just a simple/native looking flyout and update it once 21H2 is out or about to be released. The idea is great but it should sync well with the design language of windows 10 because there are other elements too in the taskbar which are boxy or not fluent and there can't be flyouts for every element on taskbar. Personally i would love to use this but my point is that it should dissolve with the windows taskbar, otherwise it would look odd.

I hope you can feel me.
Regards

Edit :-
Suggestion: Pls consider adding volume per app feature too so that my PC have one background app less to handle (You know which😁) .

@Samuel12321 Samuel12321 added this to the 0.10 milestone May 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants