https://bugs.kde.org/show_bug.cgi?id=500467

--- Comment #6 from gudvinr+...@gmail.com ---
(In reply to Noah Davis from comment #5)
> (In reply to gudvinr+kde from comment #4)
> > You don't have this on X11.
> 
> No, on X11 I'd have to make the same tradeoff choice.

Now that you said that, I tried to reproduce the issue on X11 using different
ways.
If I open up konsole from "sleep 3 && konsole" like I did in the reproduction
example, you do have konsole popping up above Spectacle.

> Just minimize Konsole if you launch it second or don't launch it second 
> unless you actually want to use it.

It was just a simple reproduction example. Of course I don't launch apps using
delays in my daily workflow. The real case what I've been dealing with is
trying to catch another wayland bug 489403.

When I open up thunderbird and hit "shift + print screen", it always pops up
above Spectacle. Like, with 100% reproduction rate.
And on X11 I never had this. And while I was writing this comment, I tried to
reproduce this again (on X11) and I still get thunderbird launching under
spectacle.

> because it would make it harder to switch to other windows, creating the 1st 
> issue I mentioned to a less severe degree.

Can't say for everyone of course, but for me personally there were no
situations where I'd want to switch somewhere before I finish making
screenshot. As a workaround, there could be a button that minimizes overlay but
even that would be overkill I think.
But I am not saying that this argument is bad. It's just not what I'd think
anyone needs.

> You don't create a layershell object, you enable layershell for a window

I am not well versed in wayland object naming, but I glad that you understood
what I mean in spite of me using incorrect semantics.

> I'm not sure if it could distinguish between the GUI thread being actually 
> frozen and the GUI being visually and interactively non-responsive.

I don't think that it matters from the user perspective tbh. You want GUI to be
responsive. When it isn't, you'd likely want to kill unresponsive app anyway.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to