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
Currently EyeLeo shows a notification window with counter that doesn't allow postponing (if I click it, it becomes darker but still counting in my Windows 7 - is it a bug?). Then when a start long break window appears, it only waits for a few seconds before the break, and I miss these few seconds very often.
I think EyeLeo should should use only one notification window for a long break, it should be shown for a configurable period of time (there is already a setting) and have following controls:
STOP COUNTER button that will stop counting and show MAKE A BREAK button for manual break (like in Do not lock PC while user is working #19; it will let user to easilly start long break when it is ready; there is a tray icon context menu item for long break but it is too far and easy to forget)
SKIP THIS BREAK button that may be useful if user currently is doing some very important and can't make a break (again, there is a tray icon menu item for that but it is much easier to click a button)
It also should be movable to avoid overlapping important windows to able user to move it instead of closing.
The text was updated successfully, but these errors were encountered:
Currently EyeLeo shows a notification window with counter that doesn't allow postponing (if I click it, it becomes darker but still counting in my Windows 7 - is it a bug?). Then when a start long break window appears, it only waits for a few seconds before the break, and I miss these few seconds very often.
I think EyeLeo should should use only one notification window for a long break, it should be shown for a configurable period of time (there is already a setting) and have following controls:
It also should be movable to avoid overlapping important windows to able user to move it instead of closing.
The text was updated successfully, but these errors were encountered: