mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 22:01:08 -06:00
[GH-ISSUE #632] Customizable app icon #453
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#453
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @big610 on GitHub (Sep 30, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/632
Before opening the issue, have you...?
Is your feature request related to a problem? Please describe
Workable
Describe the solution you'd like
Line Graph Numbered Brightness/Volume, Return to Default, Colored Icon.
Different monitors begin defaulted at different positions for both Brightness & Volume.
For accuracy tuning, to precise spots, a Line Graph & Numbered. Control Ability to Default to return to original position.
Example: Connected to Manufacturer A, then Connected to Manufacturer B, results in two different Brightness/Volume settings position spots.
Could you explain in your words why each monitor has a different default beginning?
Menu Bar Icon Color from Black to a colored Icon. Your choice of color from your default blue or pink to match your Icon. Easier to distinguish in the Menu Bar from Apple's all Black Icons.
Describe alternatives you've considered
Above
Anything else?
No response
@waydabber commented on GitHub (Oct 1, 2021):
Hi big610,
The new version 4.0.0 has an option to enable percentages and also tick marks. This I think should cover the request about precise spots.
Regarding the defaults, I don't think I fully understand what you mean. 3.x.x read the display upon startup so the default values came directly from the display. The new 4.0.0 version has an option to decide how the app should behave upon startup:
Also 4.0.0 better distinguishes and does not conflate different displays connected to the same port on M1 machines (as this was a problem with 3.x.x) if that is what you meant by the request.
Regarding the colored icon, I am not sure about that, as it would deviate too much from the UI recommendations of macOS - but it would be possible to add an option to set custom icons and if a user wants colored icon, that we he could have it.
@big610 commented on GitHub (Oct 1, 2021):
I've checked two different manufacturer displays with 4.0.0-beta1, resulting in the slider remaining the same.
What changed were the Default positions.
I set my Check Marks/Settings identical to your picture.
Answer to Defaults more defined:
Example: to the supplied ScreenShot with no percentages I would call this Default 100% & 20%.
Version 3 for one monitor had both Default Virgin at 70% & & 70%.
The percentages I am stating are guesses what they would display with your above ScreenShots.
Colored Icon:
All developers explain to me the UI recommendations for Apple. So yes their way around Apple, is have it in Settings to add Color to Menu Bar Icon.
@waydabber commented on GitHub (Oct 1, 2021):
Hi @big610
If with v3 you had 70%/70% as default, then it means that your mac or display were not able to read the settings from the display as it is probably incompatible with DDC read (some displays have this issue), as v3 always tried to read settings upon startup. Version 4 works a bit differently - when is started for the first time or a display is attached the first time, it will apply a default value of 100% for brightness and contrast (instead of the previous 70% - to prevent unexplained dimming especially in software mode at first start) and 12,5% for volume (this was intentionally changed from 70% as that was too loud for some as default value). These are however not applied to the display during startup (unless
Apply last saved values to displayis enabled), only the first time the user attempts to change these values. This is to prevent issues at startup with displays that behave badly when they receive DDC commands and to give the user has the ability to safely navigate to the setting which disables DDC and forces software mode. You can enableAttempt to read display settingsto make MonitorControl read settings from the display itself upon startup.I see that you are use an older macOS version. Regarding colored icons I was thinking about an option ad App Menu / Menu Icon titled
Choose alternate iconand a dropdown list where the user could choose an alternate SF Symbol and even set the color preferences for it. The problem is that SF Icons work with Big Sur minimum and the multicolor versions are supported only on Monterey. So you would benefit from this only if you could upgrade.@JoniVR commented on GitHub (Oct 1, 2021):
I'd argue against custom menu icons for multiple reasons:
@waydabber commented on GitHub (Oct 1, 2021):
Hi @JoniVR, all right, let's shelve this feature then, I agree that platform consistency is important.
@big610, don't despair, luckily MonitorControl is super customizable as the source code is freely available so you can easily change it in any way you'd like. If you are on macOS 10, then you can simply change the status icon asset to an icon of your liking here:
If you are on macOS 11+, you'll also need to change the
!MACOS10_DEBUGtext in this code segment to the textfalseso your custom icon can take precedence:You'll need to build the app afterwards of course.
@waydabber commented on GitHub (Oct 1, 2021):
I'll close this issue now. Thank you!