[Pidgin] #8799: Small adjustment to previous fix in Message Notification Plugin
Pidgin
trac at pidgin.im
Thu Jun 25 18:08:48 EDT 2009
#8799: Small adjustment to previous fix in Message Notification Plugin
-------------------------+--------------------------------------------------
Reporter: Luigiwalser | Owner: deryni
Type: defect | Status: pending
Milestone: | Component: pidgin (gtk)
Version: 2.5.5 | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Changes (by deryni):
* status: new => pending
Comment:
The issue here is that it really is difficult to cover all possible
desired outcomes.
Wanting the window to get focus when a message comes in is perfectly
reasonable (though I don't understand it).
Wanting the window to be raised when the message comes in is perfectly
reasonable.
Wanting "raise" to include unminimizing is reasonable.
*Not* wanting "raise" to include unminimizing is reasonable.
Further complicating things is the issue of how multiple desktops should
be handled (luckily this isn't something pidgin needs to deal with
directly, but is something *users* need to deal with and something that
the major desktops/window managers tend to handle terribly and with a
decided lack of user control/input).
At the moment pidgin allows the user to say:
"I want the window to raise" which means pidgin will call
gdk_window_raise (what that does offhand I'm not sure)
and
"I want the window to be shown" which means pidgin will make sure the
conversation is in a conversation window (not hidden to the buddy list,
etc.) and call gtk_window_present (what that does offhand I'm not sure).
The important thing to note here is that pidgin does not explicitely
request focus (if GTK+ does as a result of gtk_window_present that is
unfortunate but not something we are requesting specifically).
When you were describing your current behaviour the first two were with
just the "Raise" option on and the latter was with just the "Present"
option on?
Can you get a full matrix of focus prevention on/off against each single
option on/off, both options on/off (and ideally both orders of the if
blocks)? I realize that's a lot of work so feel free to say no.
--
Ticket URL: <http://developer.pidgin.im/ticket/8799#comment:9>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list