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
type backspace in "start" input field to change start time
When the "minutes" part is void, the selected date changes back to the current date (unselected).
The same happens if I "select all and cut" in the "start" field. It seems to happen whenever the time in the start field temporarily assumes an "invalid" value. It doesn't happen if I set the "start" input field to overwrite mode and just overwrite the digits of the field.
This was tested with the openSUSE hamster package, which was built from 9b557ab (@matthijskooijman's simplify-facttree-scrolling branch), which contains the fix for #674.
The text was updated successfully, but these errors were encountered:
I confirm this behavior in current master (hamster version v3.0.2-53-gd10ae12c). It also happens when editing an activity from a previous date. This could be serious because if one is not careful one could inadvertently clobber other activities on the current date.
I just had the same issue with hamster 3.0.2-5 using Gnome 44.44 and Linux 6.1.53-1-MANJARO.
Similarly it seems even if I register an event today for any duration, if the start hour is below the start hour of a day (see settings)
Hamster overrides the display of stats and shows the task belong to the day before.
So I did reset the start of day at 00:00 to avoid any bugs.
Steps to reproduce:
date-deselected.webm
When the "minutes" part is void, the selected date changes back to the current date (unselected).
The same happens if I "select all and cut" in the "start" field. It seems to happen whenever the time in the start field temporarily assumes an "invalid" value. It doesn't happen if I set the "start" input field to overwrite mode and just overwrite the digits of the field.
This was tested with the openSUSE hamster package, which was built from 9b557ab (@matthijskooijman's simplify-facttree-scrolling branch), which contains the fix for #674.
The text was updated successfully, but these errors were encountered: