I've been playing around with this for a while,
but as of yet I have found *no* way to keep the karamba themes just on the desktop. They insist on staying on top all other windows, which result in a ugly "cut-out" where it snaps my background to make it transparent. I use to browse with konq in fullscreen, and all the karamba themes will then display on top of the browser, no matter how I click and hack ;)
Is this a known problem, or am I doing something very wrong?
It could also be the fact that I'm using the KDE 3.2 beta, just so you know that =)
Thanks.
WindKin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q. All of my themes are "always on top" of the other windows in KDE 3.2.
A. This is a known issue with superkaramba 0.33, the current version (as of this writing). The unofficial fix is to edit the karamba.cpp file and change
line 2246: KWin::setState(winId(), NET::KeepBelow);
to look like...
line 2246: KWin::setType(winId(), NET::Dock);
line 2247: KWin::setState(winId(), NET::KeepBelow);
Then you can recompile and install superkaramba. For more information see http://sourceforge.net/forum/forum.php?thread_id=1033931&forum_id=67470
Oh, and make sure you uninstall it before recompiling, or at least try a 'make clean' to remove old compiled libraries and what not.
cheers,
-Ryan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know this is really lazy, but when is the next version gonna be out? I mean, if its within a week or something then i wont bother doing those script changes...
cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Superkaramba was reviewed by two major Linux magazines last month. The always on top bug has been stuck in SK since October, I believe, and a quick bug fix release was never released (although, some people on this forum have made the change and kindly posted their tarball - it might still be up and accessible through another thread if you hunt around).
The maintainer of Superkaramba posted last month that a quick revision would be out soon and then a major overhaul, to follow.
However, I'm going to suggest that if SK was reviewed (and very favourably) by two Linux mags and that simple little bug was still not fixed, then Superkaramba development is essentially dead. Even if it's not dead in theory, it's dead, de facto.
It's too bad, actually, as transparancy for widgets doesn't work in Gnome, so it would be nice to see attention paid to that on a future version, too.
I think the best thing about KDE is Superkaramba. It has enormous potential and much of that potential is already fully realized by a developer that clearly knew what he was doing. It's too bad its development has stopped.
Rory
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The fixed tarball is still up for download..
Here's the link... at least until Adam posts an official version. http://www.angelfire.com/geek/p0z3r/superkaramba-0.33a.tar.gz
If that link goes down.. let me know since angelfire has bandwidth limits per month.
cheers,
-Ryan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can host it as far as I'm concerned.. but I think I need to email Adam to see what's going on.. He posted that new work was taking place, but haven't seen anything since that post.
-Ryan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-05-16
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been reading that always on top was a 0.33 bug. How did this not get fixed in 0.34? The original post here is a year old now and was about 8 months ahead of the 0.34 release. The code has been posted numerous places (including outside of this site) which doesn't help those of us using SK as a package like rpm, but should have helped the developer(s). It's a pretty slick-looking program, but why would you use it if all of the sensors and such are just going to clutter your desktop and consume all the space?
If anyone else is frustrated with this one little year-old bug, there's an alternative, gdesklets, which is actively being developed. They have done 7 releases this year (SK has done 1) about every other month with the latest being just a week ago. Although written for gnome, it works fine (for me, at least) in KDE.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There was a problem in the 0.34 release when we thought we had the "always on top" bug fixed. Now it uses the kdeversion.h header file to fix this issue. For full details I would advise reading the cvs logs or by emailing me and I would be happy to explain the history of it.
As bugs always arise in a release for someone, somewhere, we try to fix them as we can.
The next release is coming shortly as we are gathering up all the changes and documentation, along with new examples on how to use the api.
gDesklets look nice as well. In fact I personally tried to use it in its infancy, and had problems getting it installed so was never able to use it. I may revisit it again when I have time, as I feel both gDesklets and Superkaramba are good for the community as a whole.
To answer your question as to why I use it. Well, it takes me just a few minutes to write something very functional and unique to my system's look and feel that noone else has done before. Clutter is an individual perspective, so it's all relative.
Albeit xml for the .display files is very universal and easily interpreted, I feel that the builtin python interpreter in superkaramba allowing people to write in python what they want a script/theme to do is much more readable in general.
Also, I see that excluding a handful of C files, gDesklets is written entirely in python. Reading the FAQ describes how there is a python-g memory leak issue creating a bad dependancy on the core of the application. Superkaramba is written entirely in C++, which excludes it from that particular dependancy.
Hope this answers some of your questions.
cheers,
-Ryan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been playing around with this for a while,
but as of yet I have found *no* way to keep the karamba themes just on the desktop. They insist on staying on top all other windows, which result in a ugly "cut-out" where it snaps my background to make it transparent. I use to browse with konq in fullscreen, and all the karamba themes will then display on top of the browser, no matter how I click and hack ;)
Is this a known problem, or am I doing something very wrong?
It could also be the fact that I'm using the KDE 3.2 beta, just so you know that =)
Thanks.
WindKin
Comment the following line in karamba.cpp
Change:
KWin::setType(winId(), NET::Dock);
to...
// KWin::setType(winId(), NET::Dock);
this is on line 2246 of karamba.cpp
thanks a lot, i was tryin to figure out how to fix that
how?
opened karamba.cpp (/src), commented line 2246:
//KWin::setType(winId(), NET::Dock);
but i still got the problem :(
From the up and coming FAQ:
Q. All of my themes are "always on top" of the other windows in KDE 3.2.
A. This is a known issue with superkaramba 0.33, the current version (as of this writing). The unofficial fix is to edit the karamba.cpp file and change
line 2246: KWin::setState(winId(), NET::KeepBelow);
to look like...
line 2246: KWin::setType(winId(), NET::Dock);
line 2247: KWin::setState(winId(), NET::KeepBelow);
Then you can recompile and install superkaramba. For more information see http://sourceforge.net/forum/forum.php?thread_id=1033931&forum_id=67470
Oh, and make sure you uninstall it before recompiling, or at least try a 'make clean' to remove old compiled libraries and what not.
cheers,
-Ryan
I know this is really lazy, but when is the next version gonna be out? I mean, if its within a week or something then i wont bother doing those script changes...
cheers
Superkaramba was reviewed by two major Linux magazines last month. The always on top bug has been stuck in SK since October, I believe, and a quick bug fix release was never released (although, some people on this forum have made the change and kindly posted their tarball - it might still be up and accessible through another thread if you hunt around).
The maintainer of Superkaramba posted last month that a quick revision would be out soon and then a major overhaul, to follow.
However, I'm going to suggest that if SK was reviewed (and very favourably) by two Linux mags and that simple little bug was still not fixed, then Superkaramba development is essentially dead. Even if it's not dead in theory, it's dead, de facto.
It's too bad, actually, as transparancy for widgets doesn't work in Gnome, so it would be nice to see attention paid to that on a future version, too.
I think the best thing about KDE is Superkaramba. It has enormous potential and much of that potential is already fully realized by a developer that clearly knew what he was doing. It's too bad its development has stopped.
Rory
The fixed tarball is still up for download..
Here's the link... at least until Adam posts an official version.
http://www.angelfire.com/geek/p0z3r/superkaramba-0.33a.tar.gz
If that link goes down.. let me know since angelfire has bandwidth limits per month.
cheers,
-Ryan
Ryan,
Let me know if you want me to host it and I will, until my host makes me stop.
Rory
You can host it as far as I'm concerned.. but I think I need to email Adam to see what's going on.. He posted that new work was taking place, but haven't seen anything since that post.
-Ryan
Thanks.
Your welcome.. I always like to help.
-Ryan
Doh. the link seems to be down for me...
downloads, but there is nothing in the archive... Anyone got it somewhere else? thanks.
It appears to work for me fine.
There are files in the archive when I unpack it.
Hey,
it works now. I think it was a problem with konqueror. I'm using FireFox now...
thanks
I've been reading that always on top was a 0.33 bug. How did this not get fixed in 0.34? The original post here is a year old now and was about 8 months ahead of the 0.34 release. The code has been posted numerous places (including outside of this site) which doesn't help those of us using SK as a package like rpm, but should have helped the developer(s). It's a pretty slick-looking program, but why would you use it if all of the sensors and such are just going to clutter your desktop and consume all the space?
If anyone else is frustrated with this one little year-old bug, there's an alternative, gdesklets, which is actively being developed. They have done 7 releases this year (SK has done 1) about every other month with the latest being just a week ago. Although written for gnome, it works fine (for me, at least) in KDE.
There was a problem in the 0.34 release when we thought we had the "always on top" bug fixed. Now it uses the kdeversion.h header file to fix this issue. For full details I would advise reading the cvs logs or by emailing me and I would be happy to explain the history of it.
As bugs always arise in a release for someone, somewhere, we try to fix them as we can.
The next release is coming shortly as we are gathering up all the changes and documentation, along with new examples on how to use the api.
gDesklets look nice as well. In fact I personally tried to use it in its infancy, and had problems getting it installed so was never able to use it. I may revisit it again when I have time, as I feel both gDesklets and Superkaramba are good for the community as a whole.
To answer your question as to why I use it. Well, it takes me just a few minutes to write something very functional and unique to my system's look and feel that noone else has done before. Clutter is an individual perspective, so it's all relative.
Albeit xml for the .display files is very universal and easily interpreted, I feel that the builtin python interpreter in superkaramba allowing people to write in python what they want a script/theme to do is much more readable in general.
Also, I see that excluding a handful of C files, gDesklets is written entirely in python. Reading the FAQ describes how there is a python-g memory leak issue creating a bad dependancy on the core of the application. Superkaramba is written entirely in C++, which excludes it from that particular dependancy.
Hope this answers some of your questions.
cheers,
-Ryan
i got the same problem with 0.34 version, so i downloaded 0.35 and now everything's alright
I still get the cutout with 0.35 when ontop=true is enabled with bottombar at the same time, but if only bottombar is set, all is well.