Scaling the SVG is sufficient, since all other drawing/position
operations depend on information from the SVG. With this change, Piper
should work nicely on HiDPI screens.
Fixes#281.
This simply connects the pieces: when a resync signal is emitted on the
device, we show the notification informing the user that something has
gone wrong.
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.
Deal with ratbagd disappearing in a graceful manner rather than just
exiting whenever we try to access the dbus interface next time.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reproducer:
- click on resolution A, B
- click on the + button
- click on resolution C
Now both B and C are revealed because B is still the last row and we call
toggle reveal on it.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
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>
Running piper from git/flatpak against a ratbagd without the GetSvgFd call
should produce a useful error message.
We can just assume that any failed call is a version error rather than a
programming error - ratbagd.py prints the full error to stderr so we can catch
any bugs during development.
Fixes#255
Can be tested by installing the .xml into /usr/share/metainfo/, then running
gnome-software --prefer-local (after killing any running g-s instance). This
may take a while to refresh and if you have a repo that contains piper it may
still be preferred for some reason.
Piper is under "Utilities", if the search doesn't find it immediately, wait
for a while? Or start searching for "org.freedesktop.Piper".
Technically appdata requires 16:9 screenshots but it seems to work with the
ones we have online for the wiki already (they're a little bit too high for
16:9).
Fixes#236
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Run these two commands:
flatpak-builder --user build-dir --force-clean org.freedesktop.Piper.json
flatpak-builder --run build-dir ~/code/ratbag/piper/org.freedesktop.Piper.json piper
And marvel at the piper flatpak.
This is the minimal version, it starts with two gtk-related complains that may
be fixable.
The env "XSLT_CONFIG": "pkg-config libxslt" is required for lxml to build, see
lxml PR 259 on github.
Fixes#202
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This allows us to read SVGs when we're sandboxed and don't have direct access
to the file system.
This requires an up-to-date ratbagd to get access to GetSvgFd()
See https://github.com/libratbag/libratbag/pull/523Fixes#245
Up until the currently requested minimum version, ratbagd didn't have a
--version command so an error is equivalent to 'too old'.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This is too annoying when you build in multiple different prefixes etc. and
the PATH isn't always set up. Let alone requiring distributors to install
ratbagd to build Piper.
Downgrade it to a large warning and let's hope people at least read that one.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
