Bug 374547 - [UI/UX] Setting 2 rows with launcher names and popup enabled makes widget unreadable
Summary: [UI/UX] Setting 2 rows with launcher names and popup enabled makes widget unr...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeplasma-addons
Classification: Unmaintained
Component: Quicklaunch (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-04 15:17 UTC by soee
Modified: 2022-11-29 05:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Image presenting mentioned configuration (1.81 MB, image/png)
2017-01-04 15:17 UTC, soee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description soee 2017-01-04 15:17:24 UTC
Created attachment 103193 [details]
Image presenting mentioned configuration

If we place quicklaunch widget on the panel (thin and horizontal) and configure it to use more than 1 row (it can be 2 or more), display names and show popup than whole widget is totally unreadable.

Maybe we could somehow check if space for each launcher (icon and name) is pretty small and than just render icon without names. At the moment with more than 1 row on thin panels often only fist/one letter of the launcher name is visible and icon hidden (imo icon should have priority).
Comment 1 David Rosca 2017-01-04 15:28:02 UTC
Yes, the configuration doesn't prevent you from having broken setup. Obviously in your case, you shouldn't have titles enabled as it won't fit there.
Not sure if it's a wrong behavior though.
Comment 2 soee 2017-01-05 08:25:51 UTC
When widget is placed on panel can we check its width and based on that calculate:

widget width / (total items / rows) = item width

and than:

if (item width < X) {
 render only icons
}

?
Comment 3 Justin Zobel 2022-10-30 00:37:35 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-11-14 05:15:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-11-29 05:18:50 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!