On Wed, Apr 22, 2009 at 11:20 AM, Ana Guerrero <a...@debian.org> wrote: > On Tue, Apr 21, 2009 at 07:43:36PM +0100, jrw wrote: >> Tags: patch >> >> I completely forgot about this bug, sorry :) Maybe it's too obsolete now... >> >> This patch changes the name of a bunch of variables (kde code is hard >> to understand), adds docs, and (to actually fix the bug), adds a >> signal itemSelected -> slotResetAffect... This resets the affect >> position pointer every time we select a new view so operations happen >> on the new view until the user makes a new right click. I also >> removed some calls to the reset function which are redundant now. >> >> This also fixes moving a tab after moving *to* a different tab using >> shift+arrow which I didn't notice in the original report. > > I forgot about it too, so.. :) > Current yakuake version is 2.9.4 made to work with KDE 4.2 in unstable, did > you made the patch against the KDE 3 version of the current KDE 4 one? > FWIW, I can not reproduce your problem in current KDE 4 from unstable. > > > Ana >
The patch is against the kde3 version 2.8.1-1. I don't really want to install all of kde4 to test this bug is fixed; it's a 100mb download and I'm still a bit nervous about losing the functions I rely on currently ;). Just in case I wasn't exact enough, here is a precise sequence which triggers the bug: - open yakuake - open a new terminal - click on the first terminal - open a new terminal - ctrl+shift left -> nothing happens (it's trying to move terminal #1 left) - ctrl+shift left again -> now the current terminal moves If it is fixed... well, no harm I guess, but it would be nice to see a 2.8.1-2 for the kde3 holdouts (or perhaps even yakuake-kde3 package?). Thanks for your attention. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
