This bug is a discussion on fixing a major usability problem in KMail (clicking on a folder, then putting the mouse over another folder *without* clicking will oftentimes select that second folder). As it appears that the fix just got put into qt-copy, this is a request for the Qt 3.1 in use in the various apt sources (Ralf's and Karolina's, mainly), be updated. It would be a *major* nicety for us major KMail users B-)
(yes, it's ironic that this message is being composed in mutt. i already know that, no need to point it out :-) ----- Forwarded message from Ingo Kl?cker <[EMAIL PROTECTED]> ----- Envelope-to: [EMAIL PROTECTED] From: Ingo Kl?cker <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Bug 48888] click on a folder and then move the mouse may selects wrong folder Reply-To: [EMAIL PROTECTED] Content-Description: signed data On Sunday 02 February 2003 11:20, Don Sanders wrote: > On Sunday 02 February 2003 13:01, Tim Wunder wrote: > > On Saturday 01 February 2003 12:25 pm, someone claiming to be Ingo > > Kl?cker > > > > wrote: > > > On Thursday 30 January 2003 06:54, Don Sanders wrote: > > > > IIRC the fix in KMail also fixes some other problems with > > > > keyboard navigation that the fix in Qt does not. > > > > > > Do you think it's possible to backport the fix to KDE 3.1? If > > > yes, could you please do so. > > > > Yes, please do so :-) > > The other keyboard navigation problems I refer to are the ctrl-left, > ctrl-right, ctrl-space folder navigation/selection. I don't consider > breakage of this a major bug, do people really want me to back port > that? Hmm, keyboard folder navigation/selection works without problems with KMail 1.5. According to the cvs log you broke this with your workaround for bug 48888. BTW, your fix results in many selected folders if the user drag selects several folders (click and hold left mouse button and then move the mouse over several folders). In KDE 3.1 always only one folder is selected if the user holds the mouse button down while he moves over the folder pane. IMO we should revert your workaround (which introduces very low level event handling which is much better done in QListView itself) and instead rely on the fix in Qt which I have just committed to qt-copy. Regards, Ingo ----- End forwarded message -----
