Can you make the network congestion popup appear as topmost as possible, no arguments there, but without stealing focus?
While I agree I should fix the underlying problem and not see it at all, there are times it interferes with my typing; using "SPACE" will inadvertently activate an action instead of typing it.
Some user experience / story discussion:
So far my experience with them is that "they were not supposed to be triggering" (except the time I tried to stream a shadow server over 3mbps), and I have not felt they have been helping me.
I've set min_quality/min_speed already on the server with some sane limits, but they are arbitrary.
I am not sure what those limits mean visually: I don't have a topmost status screen telling me min_quality:x, min_speed:y. And what does min_speed=30 mean? <130 ms latency? Is it bound to the FPS I am seeing?
Neither can I reliably modify them and see their real-time results analogously to the way I can modify a volume slider on an audio console and see that real-time result on the green/yellow/red leds showing the db output (or hear more/less sound).
Related to the above I don't know how network congestion works (^^^ ... I have not felt they have been helping me), or how/if it recovers (again with that small quality/speed status panel).
Is this a win10 client? Does it show up using the custom GTK notification widget rather than the regular OS one? (probably since there are buttons?) AFAIK, when showing the window on top of the stack, it will steal input focus.
Replying to Antoine Martin:
Is this a win10 client?
Does it show up using the custom GTK notification widget rather than the regular OS one? (probably since there are buttons?)
AFAIK, when showing the window on top of the stack, it will steal input focus.
😕 Okay, I guess
TortoisePlink password prompt somehow does this. If I start attaching to 2 screens at the same time, somehow it respects that I am giving my password to one window, and does not steal focus. It is not appearing topmost - I don't think it's set - but it appears "enough top of the stack".
I know it is obviously not the same software as yours, but it could used as a working reference point
And I guess it doesn't make sense for me to hold the ticket.
Done in r26892.
Could be backported as a fix.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2655