Jameshfisher Newbie

Joined: 04 Feb 2010 Posts: 1
|
Posted: Fri Feb 05, 2010 7:23 am Post subject: BUG: App's workspace != workspace from which it was launched |
|
|
This bug has been, well, bugging me for years now, and I thought I would finally get around to venting it:
I do a fair amount of graphics work. Most graphics apps take a good few seconds to load, or longer. So workspaces are a great idea: I execute Inkscape in one workspace, leave it to load while I switch back to my GIMP workspace to do some different tasks; then, when I'm done with that, I switch back to the Inkscape workspace where it's all ready for me to go.
That's the theory. Unfortunately, with GNOME's workspaces, a window isn't tied to a workspace at the moment that the original application is launched -- it's instead just tied to the workspace that happens to be the active one when the window appears.
What this means is that, if I want to leave Inkscape to open 10 images, which could take a minute or more, I have to sit there at the Inkscape workspace so that the windows open in the right place. That is to say, one of my key reasons for using workspaces is made void.
I imagine the term 'workspace' to mean: you can do whatever you want in this workspace just as if it were a different computer. I understand it as a kind of graphical TTY. I understand it to mean that I can rest assured that whatever I do there won't mess around with the rest of my workspaces.
The current implementation of workspaces contravenes all the above common-sense definitions of a 'workspace', and is obviously undesirable.
Thoughts? |
|