After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 172137 - When dragging something, the "raise window after an interval on selection "doesn't work
When dragging something, the "raise window after an interval on selection "do...
Status: RESOLVED DUPLICATE of bug 154614
Product: metacity
Classification: Other
Component: general
2.10.x
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2005-03-30 17:48 UTC by Karel Demeyer
Modified: 2005-03-30 18:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Karel Demeyer 2005-03-30 17:48:07 UTC 
Please describe the problem:
When dragging something, the "raise window after an interval on selection
"doesn't work.   There should be done something to make this more pleasant too,
I think.  Like, also be able to set a key(combo)  When you hover a part of a
window and that key combo is pressed the window should be raised.  Why ?  See,
you have 2 nautilus windows open, one partly covering the other and you have to
drag a file from the window above to a directory in the underlaying window that
is not visible.  When you have no tasklist on your panel I just don't know a way
to do this right now.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Elijah Newren 2005-03-30 18:53:48 UTC 
The "raise window after an interval on selection" is meant to do something
totally different than that and isn't related at all.  Yeah, I know, it's
*super* confusing and others have tripped on it before.

So, I'll mark this as a duplicate of bug 154614 due to your summary, but that's
really only half the issue--the other half is that you'd like bug 112308 to be
fixed as well.

*** This bug has been marked as a duplicate of 154614 ***