toz/MediLog
9
51
Fork
You've already forked MediLog
3

Idea for Water Tab #170

Closed
opened 2021年05月30日 16:32:04 +02:00 by mondlicht-und-sterne · 5 comments
mondlicht-und-sterne commented 2021年05月30日 16:32:04 +02:00 (Migrated from gitlab.com)
Copy link

Installed Medilog Version beta of v2.3.0

(States of mind entered are only sample data)

I have 2 example pictures here
water1
water2

My idea was that you can not only type in 250 ml for a small coffee cup (as a size), but that Medilog has already predefined certain sizes as drinking containers.

It doesn't have to be the graphics either - if it were just there, that would work too. One then clicks on the value and has then taken this value of water.

Installed Medilog Version beta of v2.3.0 (States of mind entered are only sample data) I have 2 example pictures here ![water1](/uploads/a7a9af5b903d99bf160e3e4b06347566/water1.jpg) ![water2](/uploads/7429b810d7a081baf89e2c3c023c3930/water2.jpg) My idea was that you can not only type in 250 ml for a small coffee cup (as a size), but that Medilog has already predefined certain sizes as drinking containers. It doesn't have to be the graphics either - if it were just there, that would work too. One then clicks on the value and has then taken this value of water.
andrew-gitlab commented 2021年11月08日 01:04:16 +01:00 (Migrated from gitlab.com)
Copy link

Should this option exist, I would like an option to disable it. I frequently drink water of various volumes and don't want to figure out how to add 375ml or 425ml or 740ml by choosing pictures.

Should this option exist, I would like an option to disable it. I frequently drink water of various volumes and don't want to figure out how to add 375ml or 425ml or 740ml by choosing pictures.
mondlicht-und-sterne commented 2021年11月08日 18:15:58 +01:00 (Migrated from gitlab.com)
Copy link

@andrew-gitlab For the time being, you don't need to be afraid, it was just an idea.

@andrew-gitlab For the time being, you don't need to be afraid, it was just an idea.
toz12 commented 2021年11月08日 21:09:42 +01:00 (Migrated from gitlab.com)
Copy link

Indeed, haven't done anything in this respect yet because for one, things have slowed down a bit at my end and I am also struggling with the migration to JetPack compose. Turns out to be a lot more work than anticipated.

It's actually good to get feedback on the water tab, got so little that I was wondering if anyone is using it and therefore if it's worth the effort.

Indeed, haven't done anything in this respect yet because for one, things have slowed down a bit at my end and I am also struggling with the migration to JetPack compose. Turns out to be a lot more work than anticipated. It's actually good to get feedback on the water tab, got so little that I was wondering if anyone is using it and therefore if it's worth the effort.
andrew-gitlab commented 2021年11月12日 07:14:45 +01:00 (Migrated from gitlab.com)
Copy link

It's a good idea and I'm not afraid. An alternative is to have standard volumes for each of your icons. And let the advanced user customize them. Even more advanced is the app offer to change them to a histogram of the top 3-5 most frequently entered amounts.

It's a good idea and I'm not afraid. An alternative is to have standard volumes for each of your icons. And let the advanced user customize them. Even more advanced is the app offer to change them to a histogram of the top 3-5 most frequently entered amounts.

Necromancing this idea :-)

Necromancing this idea :-)
toz added this to the 3.7.0 milestone 2026年06月17日 17:33:10 +02:00
Sign in to join this conversation.
No Branch/Tag specified
main
3.6.0
3.3.8
master
v3.3.2
v3.2.7
v3.2.5
v3.2.1
v3.2.0
v3.1.2
v3.1.0
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v2.7.4
v3.0.3
v3.0.1
v3.0.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.3
v2.6.2
v2.6.0
v2.5.11
v2.5.10
v2.5.9
v2.5.8
v2.5.7
v2.5.6
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.4
v2.4.3
v2.4.2
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v3.7.1
v3.6.5
v3.6.4
v3.6.3
v3.6.2
v3.6.0
v3.5.1
v3.5.0
v3.4.1
v3.4.0
v3.3.11
v3.3.10
v3.3.9
v3.3.8
v3.3.7
v3.3.6
v3.3.5
v3.3.4
v3.3.3
v3.3.2
v3.2.7
v3.2.6
v3.2.5
v3.2.4
v3.2.3
v3.2.1
v3.2.0
v3.1.2
v3.1.1
v3.1.0
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v3.0.3
v3.0.2
v3.0.1
v3.0.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.3
v2.6.2
v2.6.1
v2.6.0
v2.5.11
v2.5.10
v2.5.9
v2.5.8
v2.5.7
v2.5.6
v2.5.5
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v2.3.0
v2.2.5
v2.2.4
v2.2.3
v2.2.1
v2.2.2
v2.2.0
v2.1.2
v2.1.1
v2.1.0
v2.0.6
v2.0.5
v2.0.1
v3.7.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
toz/MediLog#170
Reference in a new issue
toz/MediLog
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?