[Pidgin] #9013: Change hardcoded CLOSE_CONV_TIMEOUT_SECS to user selected value

[Pidgin]

#9013: Change hardcoded CLOSE_CONV_TIMEOUT_SECS to user selected value
--------------------+-------------------------------------------------------
 Reporter:  dlou99  |        Owner:              
     Type:  patch   |       Status:  closed      
Milestone:          |    Component:  pidgin (gtk)
  Version:  2.5.5   |   Resolution:  duplicate   
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by deryni):

 dlou99: Imagine your given scenario, you are assuming that the user
 noticed that they missed part of a message, remembers that for the
 duration of the 'black-out' period, and manually re-opens the conversation
 window during the 'IM allowed' period later. That seems like a lot of
 dependence on the user for something which should be handled better than
 that.

 I will grant that allowing people to set this timeout will solve one of
 the cases that is currently an issue (the case where the unread incoming
 message is noticed) but I think we can more productively work out
 solutions to this problem if we work on it.

 A very simple first solution would simply involve not closing conversation
 windows of currently 'active' students. This will prevent/avoid this
 problem entirely and is an incredibly low-tech solution to the problem.

 I will grant that allowing people to set this timeout will solve one of
 the cases that is currently an issue (the case where the unread incoming
 message is noticed) but it doesn't handle others (the case where they
 didn't notice it). It would be better, for example, if pidgin noticed that
 the window was closed 'immediately' after receipt of a message and as such
 that the message should not be considered read (and as such not subject to
 the closed-window culling, assuming we don't have the bug ksi seemed to
 indicate we might have).

 I'm open to further thoughts on how we can improve the actual usage case
 we are talking about rather than working around it by forcing the user to
 do the 'book-keeping'.

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