[Pidgin] #4986: automatic chat input field resizing should be optional, regression from 2.3

[Pidgin]

#4986: automatic chat input field resizing should be optional, regression from 2.3
---------------------------+------------------------------------------------
  Reporter:  swbrown       |       Owner:                   
      Type:  enhancement   |      Status:  new              
  Priority:  minor         |   Milestone:                   
 Component:  pidgin (gtk)  |     Version:  2.4.0            
Resolution:                |    Keywords:  chat input resize
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by deryni):

 Gookey:
 "What if manual sizing is disabled when automatic sizing is enabled?" is
 exactly what we have now and what people are complaining about, simply
 allowing manual resizing again doesn't fix any of the problems people have
 had with the auto-resizing code and that is something I can not accept.
 The current code *needs* fixing, if after all that fixing it is still not
 acceptable to some people adding the option (or writing a plugin, or some
 other solution) can be considered.

 I was unaware until earlier this afternoon that wrapped line spacing is
 different than inter-paragraph spacing, and I fully admit that this
 complicates the sizing more than I would like. I am still hopeful that
 this can be worked around cleanly, but that will need to be tested,
 guessing in either direction is not an answer.

 If a person sets a percentage then they are indicating that should they
 maximize the window they *want* the input area to grow to fill the same
 percentage, if they don't want that they should use a number (we could
 consider capping the percentage at some large number of lines but I think
 that is just asking for confusion and annoyance). Given that ideally both
 line counts and percentages would be allowable I think your argument here
 doesn't really hold up.

 Yes, I am aware that line counts and percentages are significantly less
 immediately obvious than dragging a handle but I think the cost is worth
 it.

 2.3.x didn't handle window maximization at all, or if you want to call "by
 expanding the chat area, and leaving the input area the same size"
 handling it then the current 2.4.0 code handles it exactly the same way.
 As would my suggestion with a minimum line count. So I don't really see
 your argument here.

 My suggestion alleviates the first two parts of your response to Sean
 intrinsically and properly set up avoids the visual "jarring" in all but
 the exceptional cases where you go over your self-defined line count.

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