[9149] in athena10
Re: [Debathena] #386: bugme isn't always always on top
daemon@ATHENA.MIT.EDU (Debathena Trac)
Sun Jun 3 11:13:30 2012
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: geofft@MIT.EDU, lfaraone@MIT.EDU, kcarnold@MIT.EDU, joeuser@MIT.EDU,
jdreed@MIT.EDU
Date: Sun, 03 Jun 2012 15:10:42 -0000
Reply-To:
Message-ID: <057.c75ce4f237c56d97dab6736acdee5b34@mit.edu>
In-Reply-To: <042.9e7ce84835f17de3310982c6b22877d3@mit.edu>
Content-Transfer-Encoding: 8bit
#386: bugme isn't always always on top
---------------------+------------------------------
Reporter: geofft | Owner: lfaraone
Type: defect | Status: assigned
Priority: trivial | Milestone: Precise Alpha
Component: -- | Resolution:
Keywords: | Upstream bug:
---------------------+------------------------------
Comment (by jdreed):
Yeah, the window manager is at fault here. If I launch bugme, and then
set, say, a terminal to be "always on top", it will honor that, and no
window-state-event or visibility-event is sent to the app. So there's no
signal for us to catch. In the example given above, even putting the line
into the update hook doesn't work. Calling .present() in the update hook
does work, but is incredibly obnoxious, so I'd like to think a bit harder
before resorting to that.
--
Ticket URL: <https://athena10.mit.edu/trac/ticket/386#comment:10>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
