Version: (using KDE 4.2.0) OS: Linux Installed from: Unlisted Binary Package The device notifier has a hard coded minimum size of 150x300. This is unreasonably large, especially on devices with smaller screens (e.g. the asus eee). Assuming most people will never have more then one or two devices attached at any one time, 150x100 seems like a better minimum.
Created attachment 30883 [details] patch to allow device notifier to shrink to 150x100 attaced trivial patch
Sounds good can someone of the plasma team look and apply this patch ?
The OP might want to look at this related bug: https://bugs.kde.org/show_bug.cgi?id=187767
My personal opinion is to keep it to minimum height at any point. For example, if no devices present then minimal height with label "No devices" (this is to make sure height doesn't become 0 :) ). And height can increase as devices plug. But there should be maximum height beyond which, there should be scrollbar.
I don't think Bug 187767 is related because it is about the width the widgets use in the panel, IMHO that is something completely different, this one is about the height of the expanded device notifier not about its icon's halo's width in the panel. When it sits in the panel it should auto adjust its height but that shouldn't happen when it sits on the desktop. When used on the desktop the user should have full control over the size. But in both cases there should be a lesser minimum height.
Hi all, i can confirm this, (From an asus eee 1000h), so i would be happy if this will be solved by somebody. Also, this may be the dupe of this: https://bugs.kde.org/show_bug.cgi?id=194888
please submit patches to http://reviewboard.kde.org that way they are more easely reviewed and noticed
SVN commit 1019368 by aseigo: put a size hint in the view, don't enforce a minimum size in the qgrahpicswidget BUG:182925 M +2 -2 devicenotifier.cpp M +3 -4 notifierdialog.cpp M +5 -0 notifierview.cpp M +5 -0 notifierview.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1019368
*** Bug 194888 has been marked as a duplicate of this bug. ***