Bug 489520 - After IOTM becomes multi-row it splits application icons into second row before filling first row full.
Summary: After IOTM becomes multi-row it splits application icons into second row befo...
Status: RESOLVED DUPLICATE of bug 488758
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (show other bugs)
Version: 6.1.1
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-30 22:37 UTC by gigastarcraft2
Modified: 2024-07-02 19:51 UTC (History)
3 users (show)

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


Attachments
IOTM (11.44 KB, image/png)
2024-06-30 22:37 UTC, gigastarcraft2
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gigastarcraft2 2024-06-30 22:37:44 UTC
Created attachment 171217 [details]
IOTM

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
After IOTM becomes multi-row it splits application icons into a second row before filling a first row full (only for small  and medium icons).

STEPS TO REPRODUCE
1. Enable multiple rows. 
2. Fill task manager with enough apps that it becomes multiple row.


OBSERVED RESULT
Task manager fills a second row before first one is full (only for a small and medium icons).

EXPECTED RESULT
Task manager fills second row after first one is full.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.9.7
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
https://imgur.com/22UKlyx
Comment 1 cwo 2024-07-01 04:40:20 UTC
See also  https://bugs.kde.org/show_bug.cgi?id=488758 for the same issue with Icons-and-Text Task Manager.
Comment 2 Nate Graham 2024-07-02 19:51:27 UTC
Both share code, so it should be the same issue.

*** This bug has been marked as a duplicate of bug 488758 ***