Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX improvement - adding dates in the past #808

Open
Dinth opened this issue Apr 19, 2024 · 1 comment
Open

UX improvement - adding dates in the past #808

Dinth opened this issue Apr 19, 2024 · 1 comment
Labels
need more info Needs more information from issue poster ui/ux Issues relating to user interface/experience

Comments

@Dinth
Copy link

Dinth commented Apr 19, 2024

Quite often i am adding in backlog of data (from the nursery system or grandma notes - she stubbornly refuses to use Baby Buddy) to the system - a lot of entries from the day or two days before and i was wondering if it would be possible the end date/time to automatically change to the start date/time (after entering it), if the start date time is more than a few hours ago? entering whole time twice, together with the whole date if the entries are from a day before, can be quite a hassle if its repeated 10+ or 20+ times. Automatic update of the end time to the starting time (so for example i could just adjust the minutes, instead of typing whole date and time) would cut that number by half automatically.
Ideally the logics could be little bit more advanced and for sleep the automatic change of date/time could be done if the start time was over 10+ hours ago (as sleeptime can last 8+ h but very rarely 10h+), but for feeding it could change the time if the start time is over 2h ago.

@cdubz
Copy link
Member

cdubz commented Apr 24, 2024

i was wondering if it would be possible the end date/time to automatically change to the start date/time (after entering it), if the start date time is more than a few hours ago?

This is interesting idea but I'd want to try to work out all the possible use cases and behaviors before changing anything here.

There is also #728 which would put control of this in the user's hands. I started some work on it previously but it was more complicated than expected (largely because of Baby Buddy's very generic form fields treatment) and I haven't gotten back to it yet. Do you think that would be a preferable solution? Or still some combination of both?

@cdubz cdubz added need more info Needs more information from issue poster ui/ux Issues relating to user interface/experience labels Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need more info Needs more information from issue poster ui/ux Issues relating to user interface/experience
Projects
None yet
Development

No branches or pull requests

2 participants