[Pidgin] #13530: FeatureRequest for supporting GNOME3 notification inline reply
Pidgin
trac at pidgin.im
Sat Apr 16 12:17:49 EDT 2011
#13530: FeatureRequest for supporting GNOME3 notification inline reply
----------------------------------------------------------+-----------------
Reporter: Hexchain | Owner: rekkanoryo
Type: plugin request | Status: new
Milestone: Plugin Suggested | Component: unclassified
Version: 2.7.11 | Resolution:
Keywords: gnome3 gnome-shell notification inline reply |
----------------------------------------------------------+-----------------
Comment(by kagesenshi):
hi hexchain,
unfortunately i'm not sure how to fix both issues.
1) this is because the notification is created by subscribing to
ConversationCreated dbus event, which, is also triggered when a
conversation window is opened. Originally I made it to subscribe to
ReceivedImMsg event, however, this does not work for 1st message as the
reference id to conversation object is 0, so the plugin wouldnt know which
conversation that message belongs to. Only on the 2nd message after a
conversation window have been created will the conversation reference
becomes a number. The plugin need the reference id for the reply mechanism
and buddy icon to work.
I'm not sure how to fix this without introducing complexity which can make
it become unreliable, pidgin crashes here if there is a dbus call that ask
for any object with reference 0. I figured out its safer to link directly
to conversation rather than trying to figure out whats the conversation
window is (which might result in reference 0). In case you did not notice
yet, the notification also closes when a conversation window is closed.
2) For this, if theres a dbus method which I can call to set the
conversation as read, it should be easily fixed, anybody reading this
ticket have clues on what to call and what the parameters?. If theres no
dbus method, yep it'll be tough to implement.
--
Ticket URL: <http://developer.pidgin.im/ticket/13530#comment:4>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list