Summary: | Layout issues - digital clock doesn't resize itself and content | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | Elias Probst <mail> |
Component: | widget-clock | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | riccardo, trance202, whn-kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Screenshot showing the cutted text
Plasma Digital Clock Space Issue |
Description
Elias Probst
2008-07-18 00:39:38 UTC
Created attachment 26225 [details]
Screenshot showing the cutted text
I've just noticed, this layout issue is gone, as soon as you restart plasma. So it's just there directly after adding the applet to the panel. Makes the bug being not that worse as I've initially thought ;-) Created attachment 26275 [details]
Plasma Digital Clock Space Issue
I think I have some related problem: I placed my digital clock on a top panel (without a task manager) and the clock takes a lot of space in the panel. It doesn't adjust to its content. See the attached screenshot I forgot to mention: I'm using KDE 4.0.99 (RC1+) in ArchLinux > I think I have some related problem: > I placed my digital clock on a top panel (without a task manager) > and the clock takes a lot of space in the panel. It doesn't adjust > to its content. > See the attached screenshot This is already described in bug#164317 and as Aaron J. Seigo told me, going to be fixed by using another layout strategy in the panels. SVN commit 885323 by sebas: Correctly update the size when the date string has changed Until now, it would lag one update (which can be the initial one giving a bad first impression) behind when determining its minimumwidth in the panel. It correctly takes as much space as needed right after startup and also after config changes. BUG:166883 M +10 -2 clock.cpp M +1 -0 clock.h WebSVN link: http://websvn.kde.org/?view=rev&revision=885323 *** Bug 174425 has been marked as a duplicate of this bug. *** *** Bug 174623 has been marked as a duplicate of this bug. *** |