* Add dpi_entry GtkEntry objects to UI file and Python.
Find and apply closest resolution in self.resolutions.
[Needed?] Store value on textbox focus in.
[Needed?] Do not apply DPI value if the same as previous value.
DPI entry and resolution sliders affect each others' values.
* Remove pointless recursive logic.
Remove focus methods.
* Calculate DPI text box width based on max supported resolution.
* Renamed methods/signals to be consistent with current convention.
* Add a 'focus-in-event' signal to the DPI entry field.
Pass reference to ResolutionsPage when initialising ResolutionRow.
Use reference to invoke `ResolutionsPage._on_row_activated()`.
Do not toggle Revealer on DPI entry text box focus-in-event if Revealer is already expanded.
Grammar: dpi -> DPI
* Add type hints.
Prefix unused vars with underscores.
Actioned suggested import order from linter.
* Actually apply the closest res value (oops).
Apply the res value on focus-out-event.
* Toggle allow editing of DPI entry if 'disable' button clicked.
* Use set_sensitive() on DPI entry.
* rm pointless var.
* Create custom class for DPI text entry to circumvent assertion warning.
Grab DPIEntry focus when revealing ResolutionRow.
Revert import order.
Removed unused 'previous DPI value' var.
Remove 'private' convention underscore from ResolutionsPage._on_row_activate().
Remove callback method for DPI entry on ResolutionRow.
UI file uses DPIEntry.
Remove insert-text signal for DPIEntry from UI file.
* Line lengths
* Removed unused import.
Underscored unused parameter (PEP convention).
* Reverted underscore convention as to not break existing stuff.
* Use underscore convention, but also use it when invoking the method.
* Renamed handler name for ResolutionsPage to match method.
* Clarified docstring.
---------
Co-authored-by: Dan <64416644+brittle-bones@users.noreply.github.com>
Using a Quit button is an anti-pattern and might be confusing for users
expecting the quit button to be on the same position as of other apps'.
Note that the button is on the left and by default the close button is
on the right.
If we start not doing any commits for a year, then we can change this.
Meanwhile, this will do.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
I sincerely doubt anyone is looking at this, and it currently needs manual
updating too. Let's just drop it, it's all in the git log anyway.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Jente has indicated that he doesn't find the time to keep maintaining piper.
Let's remove him from the maintainer list, primarily to save him some
misguided emails.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
The Resync signal is emitted in a number of scenarios, so informing the
user that a commit went wrong might not be the actual problem. Hence, we
generalize the notification for all kinds of errors.
This hasn't been implemented in over a year, let's hide it from sight. Maybe
that spurns someone on to actually implement it.
It's an improvement to the GUI either way because the message printed to stdout
wouldn't be seen by most users starting the Piper through e.g. gnome shell. So
it just looks like the button is broken.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
From git shortlog, with the emails removed because I'm pretty sure just
because you sent a patch once to piper doesn't mean everyone needs to know
your email address.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
libratbag/libratbag#422 introduced effect duration in ms for LEDs as opposed to
effect rate in Hz, as was discussed in #175. This commit updates Piper's
UI to reflect these changes.
Fixes#175.
Ah, what a beautiful night sky...
The CSS background taken from the control-center scroll test page. Apparently
we can't use the SVG background and have to do this manually.
Fixes#45
