[Feature request]: Incrementally increasing complexity of subsequent postponements of the same long break

[AKagitin]

Version

• I'm using version 1.16

Existing requests

• I've checked Existing requests

Advanced Preferences

• I've checked Advanced Preferences

What operating system are you using?

Windows

Operating System Version

Windows 10

Problem description

I'm always frustrated I understand that have postponed a break. But sometimes it is necessary, so blocking of this possibility is not a good solution.

Possible solution

I think that the best way is to make more complex to postpone the same break in 2nd, 3rd, ..., time in the following fashion:
User must to enter a number how many times he/she already have postponed this break. I think this variant will be good as it will encourage the user to remember his actions and so to better control his/her behavior. If he/she fails then the break will last as planned accordingly to settings.

Thank you for the good app!
With best regards, Anatoly

Alternative solutions

User must to click the "Skip..." button more than one time (incrementally on each user's decision to postpone the same break).

Additional information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[hovancik]

Not exactly what you ask, but you can play a bit with how postpone works currently: https://github.com/hovancik/stretchly?tab=readme-ov-file#editing-postpone-functionality-