[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 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).

 The above handles case one. Case two is unfortunate but not something I
 think this feature should be designed to handle. If the teacher responds
 in a way that the student cannot relate to the question they asked then I
 would fault the teacher for answering poorly, fault the student for not
 remembering the question, fault the student for closing a window that
 still contains information they need (I routinely keep conversation
 windows open for days at a time because they act as reminders of things I
 need to do and containers for the information I need about the tasks), and
 fault the student for not following up and getting clarification. None of
 these faults is grevious or even beyond minor, but they remain things I
 just don't think the system should be designed to work around (especially
 not this system).

 Logging methods are addable via plugins, if someone wanted to write a 'log
 in memory until program close' plugin they could do so, and I would
 support their efforts. I don't know if that plugin would interact well
 with the default history plugin (it might, it might not, I just don't
 know) but if it doesn't then that plugin could provide its own history
 feature as well. This would be a much better way to handle this usage.

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