31 Aug
2009
31 Aug
'09
11:31 a.m.
Comment and
vote here:
https://bugs.kde.org/show_bug.cgi?id=162368
Thanks for finding this bug report. My issues have been already mentioned in comment #3
and James Richard Tyrer is working on it. So I'm curious about the new version of
the
clock plasmoid.
Your input and research is very much needed there. Thanks!
> And regarding vertical panels you have to multiply this issue by 3, as
> you can see in the nice screenshots in the second bug report)
> And sorry, but whenever I see this over dimensioned KDE4 battery plasmoid
> I have to laugh. It's so big but it's only able to show _5 different
states_!
> That leads actually to this problem that you cannot distinguish between 38%
> and 62%, because both states are represented by 2 bars. Well, I would be
> interested in this difference, especially when the battery runs low.
> I will never understand why some developers love to hide useful information.
>
> But to see the differences to KDE3, let's compare the KDE4 battery plasmoid
> with KLaptop. KLaptop uses only 1/4 of the icon size, but is able to represent
> _81 different battery states_ (in 5x16 pixels)! The trick is to use not only
> a vertical progress bar but another the horizontal progress bar in each pixel
> row. When I saw this for the first time (some years ago) I was fascinated by
> this brilliant idea and thought: Yeah, that's one of the reasons I'm
using
> KDE!
>
I've filed a bug addressing the super-size battery plasmoid without useful
information:
https://bugs.kde.org/show_bug.cgi?id=205707
You're welcome to post comments or vote for it.
Can you check
that against other tree views in KDE and either confirm
that this is inconsistent with the rest of KDE, or that all of KDE
needs to be improved here. Thanks!
Hm, I couldn't find another KDE application with a tree so fast. Sorry.
* moving the slider between the tree and the current
settings does not work.
But in some cases it would be necessary.
I do not understand, could you be more specific? Thanks. 
As long as it is not needed I don't want to have a
horizontal scrollbar in the
tree. That's why I would try to use the splitter to resize the tree.
I agree, I would even prefer to see lines wrap than a horizontal
scrollbar appearing! I filed this:
https://bugs.kde.org/show_bug.cgi?id=205780
If you want to attach your second screenshot there, it would be great.
But also apparently minor issues like the navigation
in trees are important
for. Fast keyword work was always one of the key features of KDE3, I think.
Sadly in KDE4 the possibility of keyboard navigation was completely ignored.
Just try to save a screenhot in ksnapshot by using only the keyboard. You
can navigate to a directory and press ENTER. Instead of changing into this
directory, ksnapshot thinks you want to enter the dir AND save the file
afterwards. Strange implementation! I would never expect both actions at the
same time.
Please write a "this is what I did, this is what I expected, this is
what happened" format, I'll verify and file it. but make sure that you
are on KDE 4.3 first, as it is a bit different than KDE 4.2. Thanks!