You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I optionally donated to support the Fossify mission.
Feature description
Provide option to disable dimming of past tasks when they haven't been marked as completed (widget only).
Why do you want this feature?
Currently the 'dim past events' option affects both events and tasks, and applies simultaneously to the APP and widget.
Within the APP, the behavior works as desirable (the tasks are only dimmed after they have been marked as completed).
The issue is with the widget (calendar monthly), that regardless of tasks' completed state, they are always dimmed once the task time has passed.
With the current behavior - it's very easy to mistake dimmed uncompleted tasks with dimmed completed tasks, since the dimming effect is visually stronger than the strikethrough.
Additional information
No response
The text was updated successfully, but these errors were encountered:
ekogupta
changed the title
Option to disable dimming of past tasks when uncompleted (widget only)
Disable dimming of past tasks when uncompleted (widget only)
Apr 4, 2024
Checklist
Feature description
Provide option to disable dimming of past tasks when they haven't been marked as completed (widget only).
Why do you want this feature?
Currently the 'dim past events' option affects both events and tasks, and applies simultaneously to the APP and widget.
Within the APP, the behavior works as desirable (the tasks are only dimmed after they have been marked as completed).
The issue is with the widget (calendar monthly), that regardless of tasks' completed state, they are always dimmed once the task time has passed.
With the current behavior - it's very easy to mistake dimmed uncompleted tasks with dimmed completed tasks, since the dimming effect is visually stronger than the strikethrough.
Additional information
No response
The text was updated successfully, but these errors were encountered: