@smoadrareun do you mean the flyout incorrectly changes, or the system unmutes.
Did this happen before installing ModernFlyouts?
@smoadrareun do you mean the flyout incorrectly changes, or the system unmutes.
The system is unmuted after log out or restart
Did this happen before installing ModernFlyouts?
No, when I exit the app, everything is ok
Ohhhhhhhhh! I get it now.
Now I know why this issue occurs.
On startup our app sends virtual volume key press signals to create the native flyout and replaces it.
While sending the signal, the system will automatically unmute.
I'll see what I can do.
Related to #115
Ohhhhhhhhh! I get it now.
Now I know why this issue occurs.
On startup our app sends virtual volume key press signals to create the native flyout and replaces it.
While sending the signal, the system will automatically unmute.
I'll see what I can do.
Instead of volume buttons, trigger a caps lock on-off signal.
Instead of volume buttons, trigger a caps lock on-off signal.
Windows doesn't have a flyout for lock keys!
Brightness and Airplane mode signals can't be stimulated.
The only option to capture the native flyouts is to send either volume keys or media keys.
While sending media key signals is non-problematic, the native flyout will only respond to media keys when there is atleast one media playback session. Which is not possible at startup.
So sending the volume key signals was the only way.
Oh ok. So impossible instead of simple. 馃槀
No, not "impossible". We can fetch the native window while it's being created on its own and store the handles instead of us forcing it to be created. But I'm not sure though.
Fixed by 0dbf40f88b7619aca1eead72ca375ccbf603c6d5.
I assure you it won't happen again.
Most helpful comment
Fixed by 0dbf40f88b7619aca1eead72ca375ccbf603c6d5.
I assure you it won't happen again.