[Pidgin] #14818: [PATCH] Finch should handle conversation-extended signals

[Pidgin]

#14818: [PATCH] Finch should handle conversation-extended signals
----------------------------------+-----------------------------------------
 Reporter:  hyc                   |        Owner:  sadrul             
     Type:  patch                 |       Status:  pending            
Milestone:                        |    Component:  finch (gnt/ncurses)
  Version:  2.10.0                |   Resolution:                     
 Keywords:  signals conversation  |  
----------------------------------+-----------------------------------------
Changes (by hyc):

  * status:  pending => new


Comment:

 Replying to [comment:4 bleeter]:
 > Just a thought, the Pidgin GTK patch should possibly be in a separate
 ticket with an explanation of why it's needed.
 > It's not immediately clear (I'm still pulling down the mtn DB of Pidgin)
 why a Finch patch should include a Pidgin patch. To my mind, as two
 different products sitting above libpurple, they should be two patches -
 particularly as the Component reported against would be different unless
 there's a compelling reason why not.
 > Your thoughts and comments eagerly sought.

 You're probably right. I just included it here because it's a small patch,
 it's a related area of functionality, and it was prompted by the work I'm
 doing with the OTR plugin. Basically, I want to be able to use
 purple_conversation_update(conv, PURPLE_CONV_UPDATE_FEATURES) to force the
 conversation's plugin menu to also be regenerated. We can split it out if
 that's better, but I don't want it to fall thru the cracks.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/14818#comment:5>
Pidgin <http://pidgin.im>
Pidgin