[Pidgin] #6459: Mouse wheel events dropped and passed through to window manager

Pidgin trac at pidgin.im
Wed Jul 30 05:35:37 EDT 2008

#6459: Mouse wheel events dropped and passed through to window manager
 Reporter:  ftfred                          |       Type:  defect
   Status:  new                             |   Priority:  minor 
Component:  pidgin (gtk)                    |    Version:  2.4.3 
 Keywords:  wheel mouse scroll drop events  |    Pending:  0     
 As the title says, when you scroll quickly in the Buddy List window,
 sometimes some of the wheel events are allowed to drop un-handled to the
 background behind the app window. This results in a rapid scroll through X
 workspaces and associated redraw costs from all of those apps. This bug
 has been present for quite a while (multiple versions) and is still
 present in 2.4.3. I can easily reproduce this if required and could take a
 video to prove it if desired, but if you just give your mouse wheel a
 quick high speed scroll (as you would always and regularly do to get from
 the top of your huge buddy list to the bottom quickly for example) you
 should see it occurring. My dev opinion of this without having read your
 code at all is that these events should be caught and ignored if they
 can't be handled in a timely fashion. Allowing events for pidgin to go to
 a different app is very bad behaviour IMO. I hope it's a bug (accidental)
 and not a design feature (on purpose) :-)

 '''Platform :'''[[BR]]
 nvidia driver[[BR]]
 debian unstable[[BR]]
 uname -a : Linux rwdlsd 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008
 i686 GNU/Linux[[BR]]

 Additionally and unrelated I share the minor niggle that others have been
 warring over :

 input box size.

 I also have a large screen and have pidgin maxed on one desktop. It looks
 bad like that and as others have stated difficult to aim your mouse at in
 a hurry. All you need to do is put a configurable minimum lines in the
 prefs to fix that for me... I kinda like the auto scroll, but I didn't
 like it at first, it grew on me. The small entry is unlikely to grow on me
 though as I've been using it for a while now and still would prefer it

 As a further aside, although the majority of people complaining about that
 change are total wankers, and I had a great laugh reading through some of
 it before I got bored, they do have a fair number of valid points in many
 cases. I don't personally agree with some of their issues, but the
 principles are sound. For the record I also dumb a lot of code chunks and
 large quotes through the client, enough to hit the message size limits of
 the aim/msn protocols fairly regularly, though I didn't get the first cut
 with the limited scrolling "feature" so the change didn't affect me.

 Why is this in a bug report about scrolling? To get the point across
 quietly and clearly without the distraction of the flame war in the other
 page. Also because I wouldn't have bothered mentioning it at all except
 for the scroll bug which didn't get resolved over multiple releases. I'm
 not enough of a tosser to post a bug report/comment about the input box
 thing by itself.

 Thanks for an otherwise good basic chat client.

 Thanks for fixing the "cut restores the line before" bug too, that was
 annoying :-)


Ticket URL: <http://developer.pidgin.im/ticket/6459>
Pidgin <http://pidgin.im>

More information about the Tracker mailing list