Version: (using KDE KDE 3.1) Installed from: Debian stable Packages OS: Linux In kde 3.0.x I always used kasbar vertically along the righthand side of my desktop. This was great since the transparancy 'feature' meant that kasbar wouldn't actually take up the whole height of the desktop. In kde 3.1, it seems that all the 'empty' space (after my N application icons) is now the background color of kicker. I don't know what else to say to help reproduce this but I have confirmed that this is not just my install/config as another user replicated the problem on Slackware 8/KDE 3.1 (that he compiled himself). I am using debian/kde 3.1 with packages retrieved from http://devel-home.kde.org/~nolden/kde/.
Subject: Re: New: empty space not transparent Does this remain the case if you go to the properties dialog and deselect the transparency option, then select it again? Rich. Jordan Lederman wrote: > > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > http://bugs.kde.org/show_bug.cgi?id=53735 > Summary: empty space not transparent > Product: kicker > Version: unspecified > Platform: Debian testing > OS/Version: Linux > Status: UNCONFIRMED > Severity: normal > Priority: NOR > Component: kasbar > AssignedTo: rich@kde.org > ReportedBy: jlederma@advance.net > > Version: (using KDE KDE 3.1) > Installed from: Debian stable Packages > OS: Linux > > In kde 3.0.x I always used kasbar vertically along the righthand side of my desktop. This was great since the transparancy 'feature' meant that kasbar wouldn't actually take up the whole height of the desktop. In kde 3.1, it seems that all the 'empty' space (after my N application icons) is now the background color of kicker. I don't know what else to say to help reproduce this but I have confirmed that this is not just my install/config as another user replicated the problem on Slackware 8/KDE 3.1 (that he compiled himself). I am using debian/kde 3.1 with packages retrieved from http://devel-home.kde.org/~nolden/kde/.
Subject: Re: empty space not transparent Yes, the bar remains the same, however when I deselect the transparancy option, the icons loose thier transparancy, and it comes back right away when i click it again. --jordan On Friday 31 January 2003 2:26 pm, Richard Moore wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=53735 > > > > > ------- Additional Comments From rich@xmelegance.org 2003-01-31 20:26 > ------- Subject: Re: New: empty space not transparent > > Does this remain the case if you go to the properties dialog and > deselect the transparency option, then select it again? > > Rich. > > Jordan Lederman wrote: > > ------- You are receiving this mail because: ------- > > You are the assignee for the bug, or are watching the assignee. > > > > http://bugs.kde.org/show_bug.cgi?id=53735 > > Summary: empty space not transparent > > Product: kicker > > Version: unspecified > > Platform: Debian testing > > OS/Version: Linux > > Status: UNCONFIRMED > > Severity: normal > > Priority: NOR > > Component: kasbar > > AssignedTo: rich@kde.org > > ReportedBy: jlederma@advance.net > > > > Version: (using KDE KDE 3.1) > > Installed from: Debian stable Packages > > OS: Linux > > > > In kde 3.0.x I always used kasbar vertically along the righthand side of > > my desktop. This was great since the transparancy 'feature' meant that > > kasbar wouldn't actually take up the whole height of the desktop. In kde > > 3.1, it seems that all the 'empty' space (after my N application icons) > > is now the background color of kicker. I don't know what else to say to > > help reproduce this but I have confirmed that this is not just my > > install/config as another user replicated the problem on Slackware 8/KDE > > 3.1 (that he compiled himself). I am using debian/kde 3.1 with packages > > retrieved from http://devel-home.kde.org/~nolden/kde/.
Subject: Re: empty space not transparent Ok, I'll take a look and see if I can figure out what's going on. This code was working fine last time I looked at it... Rich. Jordan Lederman wrote: > > Yes, the bar remains the same, however when I deselect the transparancy > option, the icons loose thier transparancy, and it comes back right away when > i click it again. > --jordan > > On Friday 31 January 2003 2:26 pm, Richard Moore wrote: > > ------- You are receiving this mail because: ------- > > You reported the bug, or are watching the reporter. > > > > http://bugs.kde.org/show_bug.cgi?id=53735 > > > > > > > > > > ------- Additional Comments From rich@xmelegance.org 2003-01-31 20:26 > > ------- Subject: Re: New: empty space not transparent > > > > Does this remain the case if you go to the properties dialog and > > deselect the transparency option, then select it again? > > > > Rich. > > > > Jordan Lederman wrote: > > > ------- You are receiving this mail because: ------- > > > You are the assignee for the bug, or are watching the assignee. > > > > > > http://bugs.kde.org/show_bug.cgi?id=53735 > > > Summary: empty space not transparent > > > Product: kicker > > > Version: unspecified > > > Platform: Debian testing > > > OS/Version: Linux > > > Status: UNCONFIRMED > > > Severity: normal > > > Priority: NOR > > > Component: kasbar > > > AssignedTo: rich@kde.org > > > ReportedBy: jlederma@advance.net > > > > > > Version: (using KDE KDE 3.1) > > > Installed from: Debian stable Packages > > > OS: Linux > > > > > > In kde 3.0.x I always used kasbar vertically along the righthand side of > > > my desktop. This was great since the transparancy 'feature' meant that > > > kasbar wouldn't actually take up the whole height of the desktop. In kde > > > 3.1, it seems that all the 'empty' space (after my N application icons) > > > is now the background color of kicker. I don't know what else to say to > > > help reproduce this but I have confirmed that this is not just my > > > install/config as another user replicated the problem on Slackware 8/KDE > > > 3.1 (that he compiled himself). I am using debian/kde 3.1 with packages > > > retrieved from http://devel-home.kde.org/~nolden/kde/.
Rich, I had assumed that this was becuase of my videocard/driver (radeon m9) but I've confirmed this on two other kde boxen (3.1.1 & 3.1.2) both with different nvidia cards. --jordan
Subject: Re: empty space not transparent > ------- Additional Comments From jlederma@advance.net 2003-05-20 17:54 > ------- Rich, > I had assumed that this was becuase of my videocard/driver (radeon m9) > but I've confirmed this on two other kde boxen (3.1.1 & 3.1.2) both with > different nvidia cards. > --jordan I have nearly finished writing a new more efficient rendering implementation for kasbar (along with number of pretty major enhancements), with luck it should be finished in time for 3.2 (though it is backwards compatible with 3.1). Cheers Rich.
I can constate this bug on kde 3.1.2 recompiled from the scratch on a suse 8.1 laptop with gcc 3.x. The graphic card is an ATI.the bug must have come in since 3.1.0, since I compiled this on a sparc station and everything is fine.Can you give me at least a hint howto fix it without waiting for kde 3.2?Or make it sense to use the latest code of kasbar of cvs?regardsrainald
I was lurking a bit in the kasbar code due to this problem. kasbar.cpp does it's handling correct. IMHO the problem is that kasbar don't know about the size of the whole kasbarextension, so it can only set it's own widget to transparency. Wouldn't it be a good solution to move the transparency stuff to KPanelExtension? So even all other extensions might profite of this. regards rainald
Any status on this bug? will it be fixed for 3.2? /me prays for it
*** Bug 36806 has been marked as a duplicate of this bug. ***
Subject: kdebase/kicker/extensions/kasbar CVS commit by rich: - Removed duplicated config loading code from the extension class. - Removed redundant reload of configuration info. - Reworked painting - Double buffering is now handled by KasBar not the items. - Items now longer force an immediate repaint, they use update instead. - Fixes #53735 CCMAIL: 53735-done@bugs.kde.org M +17 -6 kasbar.cpp 1.27 M +3 -1 kasbar.h 1.23 M +3 -51 kasbarextension.cpp 1.24 M +1 -4 kasbarextension.h 1.8 M +16 -20 kasitem.cpp 1.20 M +3 -7 kasitem.h 1.13 M +31 -23 kasprefsdlg.cpp 1.16 M +5 -2 kasprefsdlg.h 1.8 M +1 -3 kasstartupitem.cpp 1.12 M +9 -4 kastasker.cpp 1.27 M +1 -8 kastasker.h 1.19
The bug is still alive in 3.1.95. I installed the SuSE -packages yesterday and the problem remains. I traced down the code now a little bit and it seems to be not a bug of kasbar (the resizing in kasbar.cpp and kasbarextension.cpp is ok), but in the underlaying class PanelContainer in kicker/core: From my humble traces it looks like only the signal updateLayout() will be handled and this leads always to the maximum screen size of the panel or the size given in the settings (see: resetLayout()). In short terms, the PanelContainer don't and won't know nothing of the actual size of the kasbar. It looks like there is some code to handle a sizeHint() via DCOP, but I didn't fully understood it and maybe that there's a bug inside -:( Hope this helps a little Rainald
Created attachment 4324 [details] ksabar configuration see my comment
Grmmbl, my comment seems to be gone again !!! So for the 3rd time: - Problem solved - configure kasbar to length 1%, switch 'enabel to fit contents' on - everything works fine regards rainald