Skip to content

Add daily brightness automations#1866

Open
TheEveEye wants to merge 2 commits into
MonitorControl:mainfrom
TheEveEye:feat/daily-brightness-automations
Open

Add daily brightness automations#1866
TheEveEye wants to merge 2 commits into
MonitorControl:mainfrom
TheEveEye:feat/daily-brightness-automations

Conversation

@TheEveEye

Copy link
Copy Markdown

Adds a new UI panel for users to create automations for their screens' brightness to be set to a specified value at a set time, daily.
Solves #1865
Handles:

  • Device sleep: Sets the brightness to what it was supposed to be set to once able
  • Specific screens/all screens: Allows the user to select which screens should be affected
  • Enable/Disable: Users can enable and disable automations without deleting them

Dark mode:
Screenshot 2026-05-01 at 09 46 51
Screenshot 2026-05-01 at 09 47 01


Light mode:
Screenshot 2026-05-01 at 09 47 28
Screenshot 2026-05-01 at 09 47 35

@TheEveEye

Copy link
Copy Markdown
Author

Also hey maybe this project could migrate to SwiftUI at some point. Because I hate AppKit with a passion

@waydabber

Copy link
Copy Markdown
Member

Thank you.

Yes, a SwiftUI transition would be needed (along with all kinds of other updates). I was thinking about downscaling BetterDisplay to a MonitorControl 5, but that project is stuck right now.

Question before review: is the code purely your own work or the product of an AI? I have no issues with AI, just asking as I am generally thinking about how to move forward with my role as maintainer especially as there seems to be an increased "community spirit and productivity" in creating PRs, however most of it is AI coded. I am just not sure what to do about this or how to engage with all the influx of code from various contributors and what does this even mean to an open source project like MonitorControl.

@waydabber waydabber added in progress Issue currently being worked on feedback needed from reporter Waiting for issue reporter to provide feedback (see comments) labels May 1, 2026
@TheEveEye

Copy link
Copy Markdown
Author

Yes, the work is a product of AI, but I rigorously test the created code and iterate on results so it does not become "AI slop". I have a vision and always ensure that AI creates what I want without any side effects. For example, the UI of the new window I sketched out a wireframe in Figma and used that as input to explain my idea to Codex.

I don't have experience with AppKit, which would've made this a big effort for me to code manually. I have real world experience writing SwiftUI code, but not AppKit.

@TheEveEye

TheEveEye commented May 1, 2026

Copy link
Copy Markdown
Author

I was looking at some of the other open PRs and also some of the closed ones and I also labelled most of them as vibecoded mess without any kind of thought going into them. If I was maintaining this repo then I would only consider PRs where time and thought was actually put into them and not just a single prompt

@waydabber

Copy link
Copy Markdown
Member

Right. We seem to be entering an age when anybody can make anything out of any open source code in a matter of hours (or with thought put into it, days) or even just build anything from scratch in AI (which can freely reuse any existing code on GitHub anyway, sometimes in a more clever/modern/elegant way than original). I think the more sensible approach is probably to simply stop accepting PRs from non-maintainers - if somebody really wants to contribute, he has to be accepted as a maintainer and has to have an adequate skill in all technologies involved? But still, anybody can create a fork and develop (or vibe-code) the app into any direction they want. Then some forks may even get more popularity than the original project. This obviously dilutes somewhat what an original repo even means or what an app like "MonitorControl" means. Maybe I should just have a discussion thread where anybody can advertise his own fork and special added feature. Does this make sense?

@wilmer669

Copy link
Copy Markdown

how do i get autoclicker on scool crombook

@waydabber waydabber added AI contribution / fork recommendation Unplanned PR (typically AI) with improvements which may be of interest to the community and removed in progress Issue currently being worked on feedback needed from reporter Waiting for issue reporter to provide feedback (see comments) labels May 9, 2026
@waydabber

Copy link
Copy Markdown
Member

Note: As AI generated PRs are getting more numerous now, I made decision that I won't review AI generated PRs/forks due to lack of time and resources. Of course other maintainers can help with this. I will not close such PRs however, but add a fork recommendation label so these forks are visible here for anybody who might be interested in this specific addition. If this is an original (non-AI) work with major effort involved, please let me know - I want to better honor such PRs and provide a more appropriate feedback as soon as I have the time. Thank you for your understanding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI contribution / fork recommendation Unplanned PR (typically AI) with improvements which may be of interest to the community

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants