Bug 275603

Summary:	widget-clock use two lines, when both date and time is present
Product:	[Plasma] plasma4	Reporter:	Oleg Kostyuk <cub.uanic>
Component:	widget-clock	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	bloodse3ker, gregor, myriam
Priority:	NOR
Version:	4.6.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Oleg Kostyuk 2011-06-13 23:47:51 UTC

Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

widget-clock use two lines, when both date and time is present, and this leads to smaller fonts is used. in kde3 when clock show both date and time, only one line was used (and so widget was wider), and so will be possible to use bigger fonts. for now (in kde4), there is no option to restore old behavior, or to select how date and time show be shown - in one line or in two lines - when both of them is present.

Reproducible: Always

Steps to Reproduce:
Configure widget to show both date and time

Actual Results:  
Widget displays date under time, on next line, very small fonts is used.

Expected Results:  
Widget displays date and time in same line, one after another; both date and time displayed with fonts of same size.

Comment 1 Boris Yonchev 2012-01-06 16:56:19 UTC

I think this is a feature request. It's this way because on low resolution displays the clock will occupy a big part of the panel

Comment 2 Nate Graham 2018-06-08 20:02:59 UTC

Hello!

This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable.

Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham