- Jun 22, 2021
-
-
Kali Kaneko authored
- Cloases: #470
-
Kali Kaneko authored
-
Kali Kaneko authored
-
- Jun 14, 2021
-
-
Kali Kaneko authored
-
- Jun 01, 2021
-
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
webapi mainly for tests, but it's usable too
-
- May 17, 2021
-
-
Kali Kaneko authored
-
- May 04, 2021
-
-
Kali Kaneko authored
-
Kali Kaneko authored
this is mainly a workaround for #497
-
Kali Kaneko authored
-
And use the fullness to display the status.
-
-
-
-
-
We just care about locations and fullness.
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
Kali Kaneko authored
-
- Mar 11, 2021
-
-
Kali Kaneko authored
There's some corner cases that were very badly captured. On the first place, it's confusing to quit on connection errors. Secondly, a side-effect of aborting the initialization of the bitmask object was a semi-random segfault when trying to access the object. Here I pass any connection errors to the gui, but leave to the user to quit the app. This probably will need more work when we want to terminate the app on unrecoverable errors (no polkit, etc...), but for now it makes the systray much more usable. - Resolves: #465
-
a rather annoying bug, since it keeps popping up for every status change. to be included in a hotfix for 0.21.2 release. - Release: 0.21.2 - Closes: #459
-
- Mar 03, 2021
-
-
Kali Kaneko authored
-
Kali Kaneko authored
-