-
Notifications
You must be signed in to change notification settings - Fork 214
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
Read in Volume #11
Comments
Once upon a time ... exactly that, which you describe, existed in bug.n. I removed it because it had a dependency to other libraries (COM and VA) for making it work with Windows >= Vista. -- But since AutoHotkey v1.1.10 the necessary functionality seems to be included in SoundGet :-) The only problem is, that it would need an extra field in the bar, which leads to a lot of code rearrangment. The alternative would be to integrate it into the multi-purpose text field, but then without a progress bar and with no status indication using different colors. Any comments? |
For example like this: "VOL: m 50%" with 804e28c |
That certainly seems to work. I don't mind the lack of progress bar. I can see why it would be a lot of work to add it. Thanks for the quick work. Quite amazing. |
Well then, I will leave it at this. I will keep the additional field in mind for the next major release; I wanted to revise some of the code related to the bar (i. e. the color configuration) anyway. |
Feature
Read in volume
Reason
The default Windows taskbar shows battery, volume (approximated and whether or not it's muted), and time. The bug.n bar replaces most of these and adds disk, CPU, memory, and network readings.
I think that volume is a natural extension of this.
Thoughts
Use SoundGet
Could display a bar similar to the battery bar with "VOL: 00%" and maybe when muted "VOL:MUTE". That, or display a different color when the volume is muted, as technically you still have a volume level. So it could be "VOL: 50%" in a color, then when muted it could keep that text but display a different color. This runs the risk of mal-configuration leading to a bad user experience, though.
Then the config line could be something like
Config_readinVol=1
The text was updated successfully, but these errors were encountered: