Bug 438502 - Month and Year view is "overpopulated" with dots showing events
Summary: Month and Year view is "overpopulated" with dots showing events
Status: RESOLVED DUPLICATE of bug 436999
Alias: None
Product: plasmashell
Classification: Plasma
Component: Digital Clock (show other bugs)
Version: 5.22.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-12 11:58 UTC by KDamian
Modified: 2021-06-12 13:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Dots being shown in Month view (43.13 KB, image/png)
2021-06-12 11:58 UTC, KDamian
Details
Day view correctly showing the dots. (41.09 KB, image/png)
2021-06-12 11:59 UTC, KDamian
Details
Dots being shown in Year view (33.83 KB, image/png)
2021-06-12 12:01 UTC, KDamian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description KDamian 2021-06-12 11:58:34 UTC
Created attachment 139249 [details]
Dots being shown in Month view

SUMMARY

I am not sure if it is by design or not, but both Month and Year view show row of dots (symbolizing events).

STEPS TO REPRODUCE
1. Enable showing events in Digital Clock (I have PIM with Google Calendar connected via KOrganizer.
2. Open the Digital clock's calendar view
3. Switch to either Month or Year view

OBSERVED RESULT

Both Month and Year view show dots for events.

EXPECTED RESULT

Dots with events should be visible only on Days view.


SOFTWARE/OS VERSIONS
Windows: x
macOS: x
Linux/KDE Plasma: 5.4.0-74-generic (64-bit) / KDE neon 5.22 / 
(available in About System)
KDE Plasma Version: 5.22.0
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

Wayland display server
Comment 1 KDamian 2021-06-12 11:59:57 UTC
Created attachment 139250 [details]
Day view correctly showing the dots.
Comment 2 KDamian 2021-06-12 12:01:04 UTC
Created attachment 139251 [details]
Dots being shown in Year view
Comment 3 Patrick Silva 2021-06-12 13:19:58 UTC

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