Kamil Prusko

Results 81 comments of Kamil Prusko

Tagged a release [0.22.1](https://github.com/gnome-pomodoro/gnome-pomodoro/releases/tag/0.22.1) with fixes mentioned earlier. The webcam detection caused screen overlay not to open at times. It got reverted.

Hi @sojusnik :) That's true. It's not very consistent that Skipping break and the +1 minute are only in this popup. I'll take this into account when reviewing the indicator...

Noted. I notice that my fitness tracker also formats hours as "Xd Yh" when it reaches over 24h... I'm leaning more to using "Xh Ym" consistently. Give me a week...

There's an option of using total time as a prime metric + % of time spent on breaks. In my opinion, the overview is easier to read this way. Though...

@AndreiMiculita Good points! I was considering those yellow/orange dots, to mark the interruptions (the uses of pause / rewind). The count is related context-switching, so it seems like a useful...

The work on porting the app to gtk4 and flatpak is still going. I haven't touched stats view yet, but it's next in my agenda after finishing the new preferences...

True, it's not that readable. Disabling smoothing + adding hovers for 31 bars won't be optimal either in my opinion. I'm more leaning on changing this into a heatmap: ![Z9VvW-1022270530](https://github.com/gnome-pomodoro/gnome-pomodoro/assets/1135423/9f4a0d6d-7311-483d-8045-b75b057939c5)...

Ditching the timeline and using a heatmap only could look like this: ![g125673](https://github.com/gnome-pomodoro/gnome-pomodoro/assets/1135423/fec61ead-bba2-4180-affc-32632146991b)

The issue stems from several state changes being processed sequentially and it's kinda unavoidable. Silencing `resume` would make things more unpredictable - a potential landmine for someone trying to use...

Maybe as a quick fix, the calls could be deduplicated? In your example it would execute command with `$(triggers) = resume skip disable`.