Skipping Pomodoros counts as a block option; more control for what counts as a block.

[wukiwakoto]

Is your proposal related to a problem?

Kind of? I was using Pomofocus which when you skipped to the end of a pomodoro, it would count as the full block. As well, if, let's say, you skipped too far, you were allowed to change which block you are on before your long break. However, it lacks both options.

Describe the solution you'd like

If possible, allow a setting, when enabled, skipping a Pomodoro counts as a full block instead of resetting the timer for the block. Additionally, a way to click the lines indicating the number of blocks before a break to change which block you're on would be great.

Describe alternatives you've considered

Can't say there are any alternatives for the first one. But some kind of indicator for what block we are on and clicking on it in some way to change the block count, etc.

Other information

N/A

[kamilprusko]

Are you referring to this Pomofocus? There are few projects with the same name. I've checked other projects for a more context ...

Solanum and Tomatillo:

• let you skip to desired cycle before starting the timer
• skipping is disabled once while the timer is running
• session indicator in Tomatillo is non-interactive

pomodorolm

• lets you skip to next pomodoro/break regardless whether the timer is stopped or running
• skipping a long break starts a new cycle, always
• text indicator for the session, non-interactive

Focus Timer takes a different approach since it's in part a time tracker and must work well without the full window (using GNOME Shell indicator / compact mode / keyboard shortcuts). It tries to schedule a long break according to settings (at a ~predictable intervals). The session indicator tries to represent real time spent. Skipping behaviour / marking Pomodoros as uncompleted is build around scheduling long breaks, really.

It's tempting to introduce exception for skipping Pomodoros, so they are always counted, but it would make the current behaviour less consistent. Maybe adding a choice for the completion threshold would help clarifying the current behaviour (50% / 66% / 80% / 100%)?

As to selecting which cycle is current - it does not fit well with the project in my opinion. Also it would be hacky since it's displayed based on session history - not on a simple counter. I would like to make it easier to override the number of remaining cycles for the current session though - maybe by using mouse wheel?