[Pidgin] #5630: Create Whitespace boundary for the new input box

Pidgin trac at pidgin.im
Fri Apr 25 12:19:40 EDT 2008


#5630: Create Whitespace boundary for the new input box
---------------------------+------------------------------------------------
  Reporter:  arnabdotorg   |       Owner:        
      Type:  enhancement   |      Status:  closed
  Priority:  minor         |   Milestone:        
 Component:  pidgin (gtk)  |     Version:  2.4.1 
Resolution:  wontfix       |    Keywords:        
   Pending:  0             |  
---------------------------+------------------------------------------------
Changes (by deryni):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 So a couple things here.

 First, the fact that more places don't let you click with more freedom is
 a problem, the fact that pidgin does is good. Yes, it means teaching
 people about it, and we do when it comes up. This has no real bearing on
 anything else here.

 Second, you can't "fix" the "except the tab" behaviour because that isn't
 broken. Clicking in the tab has a real usage and keyboard focus has reason
 to be there. There are tab-specific keybindings that work there and/or
 which can be added there. So fixing that exception would break other
 things.

 The typing area can't be made "more visible" it can only be made larger.
 Given that the entire window is a click target we see little reason to
 make it larger (not to mention that part of the resizing idea was to let
 it be smaller in the first place).

 If you are seeing only a single pixel of input area behind your formatting
 toolbar that is a *bug* that is largely fixed in 2.4.1 (so make sure you
 are using 2.4.1). If you are still seeing it in 2.4.1 then you are likely
 using Windows and a non-default Windows theme. You can try switching to a
 different Windows theme and back again, that may fix it. If not switching
 themes in general should. (Switching GTK+ theme may fix it also, and be
 less drastic.) This also has little bearing here.

 No, we aren't really violating Fitt's law, it mostly doesn't apply here.
 In fact by making the entire window an input area click target we have
 just about maximized the available target thus making good use of Fitt's
 law.

 Padding the input area with useless whitespace is absolutely not the right
 thing to do here, not in the slightest (especially since adding extra
 whitespace and "keep the 2 line box" are essentially diametrically opposed
 ideas). I'm going to close this because I really don't think there is
 anything new or convincing here.

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


More information about the Tracker mailing list