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

Coloured Highlighting in Blood Pressure Tab isn't Working in 3.3.7 FOSS, Build: 5499 #561

Closed
opened 2025年10月03日 21:04:52 +02:00 by oemmes · 3 comments

I tried: Dark Mode, Light Mode, Auto Mode.
I tried enable / disable dynamic colours.
I emptied the Cache in Android Apps Settings

I think it is since the last Update, last time i remember coloured highlighting was before the last Update if i remember correct.

https://social.tchncs.de/@nahtanoy/115308975722393240

I tried: Dark Mode, Light Mode, Auto Mode. I tried enable / disable dynamic colours. I emptied the Cache in Android Apps Settings I think it is since the last Update, last time i remember coloured highlighting was before the last Update if i remember correct. https://social.tchncs.de/@nahtanoy/115308975722393240
Owner
Copy link

Well, looks like you hit on a copy and paste bug 🙄
Can you check the "Highlight values" setting for the Weight tab? I am pretty sure it's set to off. Turn it on please and restart the app.

Well, looks like you hit on a copy and paste bug 🙄 Can you check the "Highlight values" setting for the Weight tab? I am pretty sure it's set to off. Turn it on please and restart the app.
Author
Copy link

It was turned on.

Turned it off, restarted App -> nothing
Turned it on again, Weight was coloured.
Restarted App -> Now Blood Pressure ist coloured again 😁

It was turned on. Turned it off, restarted App -> nothing Turned it on again, Weight was coloured. Restarted App -> Now Blood Pressure ist coloured again 😁
Owner
Copy link

Hm, strange? But anyway, we found a workaround and it will be fixed with the next release.

Hm, strange? But anyway, we found a workaround and it will be fixed with the next release.
toz added this to the (deleted) milestone 2025年10月04日 12:39:27 +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
2 participants
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#561
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?