[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:  new         
Milestone:  Patches Needing Review  |    Component:  pidgin (gtk)
  Version:  2.5.5                   |   Resolution:              
 Keywords:                          |  
------------------------------------+---------------------------------------

Comment(by dlou99):

 Replying to [comment:15 deryni]:
 > Open conversation windows should not be being closed, if you are seeing
 that it is a bug. A bug we have had on occasion, and more than once
 believed we have fixed. If you are still seeing it with pidgin 2.5.5 then
 apparently we still have it and still need to work on fixing it (there may
 or may not be a currently open ticket for this, I'd have to search and
 don't have the time to do so at the moment)

 I don't think you are fully understanding use case 1.

 User1 and user2 have a conversation.  User1 says "bye".  User2 says "bye".
 At this point, both users think the conversation is finished.  User1
 closes the conversation window because he thinks the conversation is
 finished.  User2 changes his mind and tries to send one more message after
 he said "bye".  User1, being in the process of closing his window, only
 reads a portion of the message before he finishes clicking 'close' (or
 pressing the escape key).  This is a classic race condition.  Sometimes
 user2 can catch user1 before he closes his window, sometimes he can't.
 The "don't close immediately" pref partially corrects this race condition.
 If logging is turned off and user1 is able to reopen the conversion within
 10 minutes, then he is able to recover the portion of the message that he
 would have otherwise been unable to read.  However, if user1 is unable to
 reopen the conversation within the 10 minute timer due to outside forces
 then the message has been read from pidgin's perspective but not from
 user1's perspective because he was only able to quickly read a portion of
 it.  10 minutes makes wild assumptions about user1's availability to re-
 open the conversation that I believe are not always valid, as in the case
 of the teacher who can only use the computer 10 minutes at a time at the
 top of every hour.

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