Modernflyouts: Feature Request: Ability to control volume per-app

[Samuel12321]

One of the most requested changes from store feedback is to add individual app volume control to ModernFlyouts.

[ShankarBUS]

Woah! @Samuel12321, are you kidding me?

You do know it's very hard to do, don't you?

It will require intense work!

[Samuel12321]

hence very low priority and post v1.0 labels.

A lot of the work has already been done by the ear trumpet team. But it is something to consider in the future when the app is out of preview.

[Cyberdroid1]

Is this really required? I mean, it's just a flyout, right?

[ShankarBUS]

If it was just a flyout, I wouldn't have added new features to the GSMTC module.

LoL

@WindowsFanBoi, does this proposal somehow overlap with yours in #103?

[Cyberdroid1]

@ShankarBUS Aye Aye, captain!

Looks like it is overlapping.

[ShankarBUS]

If the EarTrumpet devs look at this and #103, they'll kick our asses lol 😂.

Our plan should not be to replace EarTrumpet. We shouldn't disgrace their app this way. Let's give it the respect it deserves 😶.

@Samuel12321, Could you edit the title to say "Ability to control volume per-app"?

And in the detail we can say similar to EarTrumpet.

But we are gonna steal code from them anyways (if we were to implement this feature) 😂.

[Cyberdroid1]

Eartrumpet is anyways open source. No trademark there. Who will stop us?

[alexeidrekker]

Perhaps a collaboration to integrate ear trumpet into modern flyout and vice versa? Not a developer, so apologies if that isn't possible and I am out of scope.

[ShankarBUS]

EarTrumpet is stable, so they won't want to have any new breaking change. Even I asked them if I could add the media controls to their app as I have some experience on that.

https://github.com/File-New-Project/EarTrumpet/issues/475

But they rejected my offer sedly 😢.

So, the only way is us integrating (stealing) features from EarTrumpet.

[Samuel12321]

technically not stealing as Ear trumpet uses a MIT licence so we can use any of their code.
Ear trumpet seems to be not actively developed at the moment, last update was in February.

[Cyberdroid1]

Yeah, it seems to have fallen to a lull moment, for now. We can "borrow" code freely. 😁😁

[alexeidrekker]

Ha ha. Fair enough. Good luck!

[riverar]

EarTrumpet dev here: We're more than happy to replace our flyout, but we have a lot of constraints (e.g. needs to be wpf, downlevel support, acrylic, have all the right accessibility, controls, high dpi, animations, etc.). Does ModernFlyouts support that?

[Samuel12321]

Hi @riverar , ModernFlyouts is wpf, high dpi, has animations, and we are working on acrylic (@ShankarBUS has managed to find a way to add acrylic without the dragging lag #68).

We are open to adding/ accepting the addition of anything you felt nessesary.

@riverar we would be more than happy to add you as a collaborator if you wanted.

@ShankarBUS any thoughts/ anything you want to add.

[ShankarBUS]

I'm just amazed! I'm too happy that they agreed to collaborate with us ❤️.

But downlevel support could be cut up to Windows 10 1809+ due to MSIX packaging.

Accessibility support needs further investigation. We need provide full accessibility support at least to the tray flyout.

Well, my acrylic method would restrict the minimum supported OS to Windows 10 1903 (due to Visual Layer dependency and reg free activation requirement).

Most of our existing user base are on Windows 10 1903+. So, I don't think this will block our path.