Power + volume down doesn’t invoke the full-screen shot. I expected it to, considering that (per https://www.reddit.com/r/pinephone/comments/17210bz/phosh_take_a_screenshit/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button) Phosh uses GNOME Shell’s underlying implementation to do so.
Spectacle isn’t installed by default, but would a default binding exist which can be invoked on a mobile device, and can one be set with these buttons (if not)?
There’s at least a shortcut in the Quick Settings area.
Additionally, spectacle should work. However, its GUI is dreadful on Mobile.
Yeah, Spectacle is not designed for mobile and probably never will be. It’s possible to make the UI convergent with enough effort, but I don’t think that would result in an app that feels good on desktop and mobile.
@ndavis, do you know of another way to capture a per-application screenshot? I often have no reason to capture the navigation and status bars too.
I’m surprised. There’s nothing fundamentally inferior about Kirigami versus QtWidgets, right?
I don’t like the former as much in its current incarnation, but I was under the impression that that was merely because it’s new.
…Of course, excepting the psuedo-windows. I’ll hate those until I die.
do you know of another way to capture a per-application screenshot?
On Plasma Mobile? Not that I’m aware of, but I’m not very familiar with Plasma Mobile. I would suggest asking in the #plasmamobile:kde.org room on Matrix if you can’t get an answer here.
I’m surprised. There’s nothing fundamentally inferior about Kirigami versus QtWidgets, right?
It depends on the exact usecase, but they’re broadly similar in capabilities. Qt Quick (what Kirigami is based on) has a significant edge with graphics related things and UI development speed while Qt Widgets has more mature components overall and better text editing components. However, that’s not very relevant here. Spectacle’s GUI is already mostly Qt Quick. The issue is that screenshot apps for mobile and desktop need to have different designs.
On mobile, you typically only have one screen and one app visible at a time. You can greatly simplify the user experience for mobile because of that. For instance, you could eliminate every capture mode other than a screen capture where cropping is optional.
On desktop, you can have any number of screens and windows with different sizes, UI scales and positions. While I could eliminate every capture mode other than rectangle mode, I know that there are people who want to use window and screen capture modes because they are quicker for certain use cases and can capture things in ways that rectangle mode can’t always do.
@ndavis, do you utilize AOSP (at least, ≥V7) at all? If not, I understand you thinking that, but that’s not whatsoever true for modern mobile OSes:
That’s a fully-fledged WM in AOSP 14, native to the OS.
In fact, I installed Spectacle explicitly so that I could utilize its “Active window” mode, to reduce how much I’d need to crop screenshots.
Thanks for the suggestion, but I prefer asynchronous methods of communication – forums – because the whole point of me asking something is to later refer back to it. That’s really hard when using Matrix, since Cerulean never took off. [1]
I use Android 12. I don’t know which version of AOSP that corresponds to, but I assume it’s AOSP 12. I’m aware that some apps can be windowed, but I never do that since there’s barely enough screen space for anything other than one app. It always seemed like a gimmick to me. Perhaps my ways and the ways of people around me are old fashioned among mobile tech enthusiasts, but I’ve never seen anyone who wasn’t a mobile tech enthusiast use the windowing capabilities.
@ndavis, yeah, it is a lot more useful when you’ve got a (portable, USB-C) display attached. I’d definitely miss it in general use if it were gone, though.
The correlation is 1:1. They’re just different names for the same thing.
