You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find it a little confusing that volume control and signal displays are colored in the same colors. I guess this is only due to personal preference, though. Thus I wonder whether having configurable foreground colors for the individual parts of the bars could be beneficial?
A patch for bf4acb3 acting as a proof-of-concept is attached.
In case it looks good enough, it is of course also possible to apply it; in case it is easier to handle, I can of course alternatively try to open a pull request instead :)
Wrt. hard to read: I think I can come up with an improved version that would use more readable names, it will just take some time :)
Regarding the configuration of the areas: I am not sure how useful this is for a "global" configuration because most likely, the "good signal" area will depend on the actual device in use? But then again, I am not really an audio expert...
Another thing that I would love to configure is the unicode characters used for drawing. Reasons: I might want to experiment with using the "large block" characters (e.g. █░▒▓) for signal strengths/loudness and regular ASCII for mute/unmute symbols (as they are not displayed correctly here and I do not want to have Emoji in my terminals anyways :) ).
I find it a little confusing that volume control and signal displays are colored in the same colors. I guess this is only due to personal preference, though. Thus I wonder whether having configurable foreground colors for the individual parts of the bars could be beneficial?
A patch for bf4acb3 acting as a proof-of-concept is attached.
In case it looks good enough, it is of course also possible to apply it; in case it is easier to handle, I can of course alternatively try to open a pull request instead :)
patch-allow-differnet-colors.txt
The text was updated successfully, but these errors were encountered: