| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Mattias Andrée <m@maandree.se>
|
| |
|
|
| |
Signed-off-by: Mattias Andrée <m@maandree.se>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Use 'redshift-status-on-symbolic' and 'redshift-statys-off-symbolic'
if available.
If these icons are not present in the icon theme, fallback to
'redshift-status-on' and 'redshift-status-off'.
Symbolic icons are the only way for themes to properly support
both light and dark panels with grey icons. If the icon name ends
with -symbolic, GTK renders the foreground color of the icon based
on the color of the panel behind it.
|
| | |
|
| |
|
|
|
|
| |
Avoids warnings generated when a GtkDialog is used without a
parent window. Also adds fixes for #220 using a solution provided
by agnivade.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Instead of calling sys.exit() the signal handlers now try to terminate
the child process. After the child exits, the process will be reaped by
the GLib callback which will call Gtk.main_quit() which will then quit
redshift-gtk. This ensures that the redshift process does not outlive
the redshift-gtk process.
|
| |
|
|
|
| |
Catch in the except block the case when the required version of
Appindicator3 is not available to also fallback in GtkStatusIcon widget.
|
| |
|
|
|
| |
Avoid another GObject Introspection warning in redshift-gtk by providing
the required version of AppIndicator3 before import it.
|
| |
|
| |
This fixes a warning when starting redshift-gtk with gtk 3.18.
|
| |
|
|
|
|
| |
This splits the user interface into, RedshiftController, a GObject
subclass that takes care of starting and interacting with the child
process, and RedshiftStatusIcon providing the actual user interface.
|
| | |
|
| |
|
|
|
|
| |
The termwait method is used to wait until the child process has
quit. Previously this would fail with an exception if the child
has already quit. This is now ignored.
|
| | |
|
| |
|
|
|
|
|
| |
This dialog is shown whenever the child process exits with a
non-zero status. The error output from stderr of the child
process is buffered in redshift-gtk in case the child exits
unexpectedly.
|
| |
|
|
| |
This also adds SIGINT to the signals handled by redshift-gtk.
|
| |
|
|
|
|
|
|
|
| |
This requires that the stderr (and stdout) are emptied when the
child process exits, otherwise redshift-gtk will exit before the
error output is forwarded. Also, the '-v' parameter is moved to
the beginning of the command line to avoid error output including
this (e.g. `redshift-gtk -l` would complain about the missing
location provided `-v`).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Mattias Andrée <maandree@operamail.com>
|
| |
|
|
|
| |
Try to set the process title during startup. Before, redshift-gtk appeared as a python process.
This change enables `pgrep redshift-gtk` or `killall redshift-gtk`.
|
| | |
|
| |
|
|
| |
Python 2 is no longer supported
|
| |
|
|
|
|
|
|
|
|
| |
This allows redshift-gtk to show the current state of the redshift
process. redshift-gtk follows the enable state of redshift and toggles
the icon accordingly.
The implementation is changed to use glib to spawn the child process
instead of relying on python subprocess module. This is necessary
because of inflexibility in the python module.
|
| | |
|
|
|
This is primarily for improved discovery. Some users report that they didn't know about redshift-gtk, but had it been available on tab completion they would have noticed. Also, I think it is in general good practice that closely related programs have the same prefix.
|
