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 101561 - ddd "Command Tool" moving
ddd "Command Tool" moving
Status: RESOLVED DUPLICATE of bug 426519
Product: metacity
Classification: Other
Component: general
unspecified
Other other
: Normal normal
: future
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2002-12-18 23:26 UTC by Matthias Clasen
Modified: 2007-04-09 22:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Clasen 2002-12-18 23:26:59 UTC
ddd has the (ugly) habit of displaying a separate toplevel "Command Tool"
and  trying to keep it in a fixed position relative to the main window. The
works with metacity until I move the "Command Tool" window to change the
position relative to the main window. Subsequent moves of the main window
have the effect that the "Command Tool" flickers around. It seems to jump
between its new relative position and the original position, with the
original position winning in the end.

I certainly agree that ddd's handling of the "Command Tool" is quite
java-IDE-esque, but metacity should either support it or deny the request
to move the "Command Tool" together with the main window. The current
flickering is even more annoying than the original ddd behaviour.
Comment 1 Havoc Pennington 2002-12-18 23:49:55 UTC
Trying this quickly and looking at metacity's verbose logging, it 
certainly looks like metacity is honoring every configure request
it gets on that window, and not doing anything else to it.
I didn't look too closely yet. Certainly need to understand in detail 
what's happening in terms of configure requests and who moves the
window when and why before knowing where the bug lives here.
Comment 2 Elijah Newren 2007-04-09 22:12:21 UTC
Flickering is gone now; looks like this was the same as bug 426519.

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