Add config

[salfel]

This PR aims to add support for a hyprsunset.conf file.

The user can set different profiles in his config, which will then be applied automatically at the provided time.

max-gamma = 100

profile {
    time = 7:30
    identity = true
}

profile {
    time = 22:00
    temperature = 5500
    gamma = 0.8
}

I have implemented it in a way, so that you could introduce as many profiles as you like. An alternative would be to provide just a day and night profile.

[salfel]

I currently made it, so that when passing --temperature or --gamma to the command, this will override the current active profile's temperature/gamma. On the next scheduled profile it would however then use the profile's temperature/gamma. Maybe this functionality has to be discussed

[salfel]

For thread safety, i have just added a lock guard in the schedule function. To my understanding this should now be thread-safe. Let me know if it isn't or if I should adopt something different

[vaxerski]

it's not enough unfortunately. wl_display_dispatch is not thread safe. Any wayland command you execute in another thread can (and eventually will) fuck up the queue and segfault.

[salfel]

it's not enough unfortunately. wl_display_dispatch is not thread safe. Any wayland command you execute in another thread can (and eventually will) fuck up the queue and segfault.

Oh, my bad. Didn't understand that the issue lies in the wl_display_dispatch. Will fix that ASAP

[vaxerski]

very nice, just a minor style nit.

[vaxerski]

also run clang-format if you havent

[salfel]

also run clang-format if you havent

already did

[vaxerski]

lgtm, just needs a wiki mr

[salfel]

I'd also like to suggest we now bump the version to 1.0, as this, in my opinion marks a big milestone in the usability of hyprsunset

[vaxerski]

I'd also like to suggest we now bump the version to 1.0, as this, in my opinion marks a big milestone in the usability of hyprsunset

we don't do 1.x

[salfel]

I'd also like to suggest we now bump the version to 1.0, as this, in my opinion marks a big milestone in the usability of hyprsunset

we don't do 1.x

oops my bad, then 0.3 right

[vaxerski]

ye