I don't think this should be limited to just cases where WM_WINDOW_ROLE
is set. As someone else commented, virtually no applications have
WM_WINDOW_ROLE set, and so only remembering window positions for apps
that do set it would not really address the problem.
Also, from the docs that someone lin
dreamon: See comment #9, and bug #391533 - I did file (a more general
version of) this bug against 100 Papercuts. It was initially rejected
for the usual storm of glib "somebody else's problem" and "it's a
feature, not a bug" reasons, but in the end 100 Papercuts rejected it
because it's not simpl
The last weeks have seen a lot of discussion on the bug, and it seems
the general consensus is that this behaviour isn't desired by most users
and is, in fact, a major issue for most people. People have pointed out
that this feature is very standard in most major operating systems and
there seems t
First, let me disagree violently with whoever classed this problem as
"Low" priority: it is, as others have already noted above, a real
productivity killer, on a system-wide basis, to have to be constantly
rearranging already arranged windows every time one opens an app anew
(not to mention the mon
"That's not a reason to make this bug invalid then, is it?"
Not really (and it wasn't me who did that). It's a good solution that we force
every application to set WM_WINDOW_ROLE properly and handle the saving and
restoring of position in the window manager.
Btw. there needs to be a maximum numb
Paul, thanks for the bug title update.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.
https://bugs.launchpad.net/bugs/124315
Title:
Remember+restore window position of applications if WM_WINDOW_ROLE set
--
des
"The code in coment #14 requires that the application set WM_WINDOW_ROLE
properly."
That's not a reason to make this bug invalid then, is it? In fact,
quite the contrary. If this bug is marked invalid, and no WM (or DE)
level support for placement is ever added, there's little incentive for
appl
I'm sure that Denny will have input here, and I'm concious that this
question sounds a little like a trap to point out where I have
overlooked the reason this would be a problem.
So, lets start from first principles...
The thing that this thread contends is that each application should not
have t
James: re: "then implement it in the window manager", could you suggest
what those heuristics would need to be? In this case it's going to
probably be harder to implement it, than to design what "should" happen,
ie what heuristics should be used. If you can specify those it would be
easier to fol
OK, so that's the answer then isn't it... have whatever library is
involved return a warning if WM_WINDOW_ROLE is not set, and then
implement it in the window manager if that value is set... It's not
unreasonable for the application to be required to do that kind of
thing... But I think it probably
10 matches
Mail list logo