[kde] [Bug 442273] New: application window opens in the currently-active desktop not the desktop where it was launched
Henry Pfeil
bugzilla_noreply at kde.org
Fri Sep 10 17:54:12 BST 2021
https://bugs.kde.org/show_bug.cgi?id=442273
Bug ID: 442273
Summary: application window opens in the currently-active
desktop not the desktop where it was launched
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: hpfeil at psnarf.org
Target Milestone: ---
SUMMARY
Software like Qt Creator, or Firefox, takes a minute from the time it is
invoked until its window appears on the desktop. While waiting, I may go to
another desktop to read a just-arrived e-mail message. Even though I launched
the application from, for example, desktop 4, its window appears in desktop 5.
Would it not be more elegant if the application window opened on the same
desktop from which it was launched? Open Qt Creator on desktop6, go to my
e-mail desktop3, Creator window opens in desktop6. When I'm finished with my
sub-task, I go back to my IDE desktop6 and Creator is up and running.
Instead, while I'm reading a message on desktop3, Creator's window opens and
obscures the message window I'm reading. Seems a bit intrusive, perhaps even a
violation of the Law of Least Astonishment.
Same with Firefox or any other program that takes a significant amount of time
after launch before its window opens.
Seems like the program busies itself setting up data structures,
initialization, allocating memory and all, then when it is ready to open its
application window, only then does it check to see which desktop on which to
open its window, which could be different than the desktop from which it was
launched. There must be a way to lock the application window to the launch
desktop, even if the currently-active desktop is different.
Linux/KDE Plasma: Slackware 15.0
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list