A GUI named hedge for smartwatch like devices based on ESP32. Currently support for T-Watch2020 (V1,V2,V3), T-Watch2021, M5Paper, M5Core2 and native Linux support for testing.
New to using pulls, I generally just modify stuff locally and don't use github, but I thought this might be nice to have merged so I apologize if I messed anything up. The changes I was looking to pull are included in bluetooth_msg.cpp and bluetooth_msg.h. The rest of my commits are for Sailfish users (with a lot more to come as I get caught up to my local files) and probably shouldn't be merged.
Previously you helped me with implementing Gadgetbridge bluetooth weather messages in bluetooth_msg.cpp. I recently took that a step farther by piggybacking on your find src icon function and including the weather conditions set forth by open weather maps as well as making a weather widget from that information. This requires no wifi at all, just the GB bluetooth weather message.
When a weather message is received it is popped up on screen with a sourced weather condition:
If the weather message is closed, you can see a weather widget that is also created with the correct weather icon and temp information. (The message icon is the weather message since it passes to the msg_chain.)
If the weather message is deleted the weather widget is retained with the correct info:
Known Issues:
Night widgets are not defined or set up. I was going to, and still could, implement a function where if int h via "%02d", h is > say 18 then search for the icon name from a night list. However the more elegant way would be to simply replace the "d" in the img name with "n" since the night icons only differ in that regard and are all the 6th character in (ex owm04d and owm04n are day and night for the same conditions). I am having trouble getting that to work however. Would appreciate any help
I made a few changes to the theme in order to get the weather icons to fit better in the message.
There can be an issue with multiple weather messages stacking up. The widget will show the correct information.... unless the user deletes the newest weather message first.
Example: weather message with clear sky, and weather message with clouds. The weather message with clouds is the newest and the widget reflects that. When opening the message_chain the newest message comes up first. If the weather message with clouds is deleted first, the weather widget would revert back to clear sky.
I wanted to keep the actual weather message as it provides more information than the icon does. Many conditions resolve down to a few icons. It would be nice to discard an old weather message when a new one comes in, not have it in the message chain, and have it accessible by the weather widget. But I have also had issues with removing the message widget. I am pretty sure I could delete the weather message after it is received via the message delete call back and the above issue would no longer exist, but we would lose the actual weather txt info. Maybe I will look to incorporate those into the widget.
New to using pulls, I generally just modify stuff locally and don't use github, but I thought this might be nice to have merged so I apologize if I messed anything up. The changes I was looking to pull are included in bluetooth_msg.cpp and bluetooth_msg.h. The rest of my commits are for Sailfish users (with a lot more to come as I get caught up to my local files) and probably shouldn't be merged.
Previously you helped me with implementing Gadgetbridge bluetooth weather messages in bluetooth_msg.cpp. I recently took that a step farther by piggybacking on your find src icon function and including the weather conditions set forth by open weather maps as well as making a weather widget from that information. This requires no wifi at all, just the GB bluetooth weather message.
When a weather message is received it is popped up on screen with a sourced weather condition:
If the weather message is closed, you can see a weather widget that is also created with the correct weather icon and temp information. (The message icon is the weather message since it passes to the msg_chain.)
If the weather message is deleted the weather widget is retained with the correct info:
Known Issues:
Night widgets are not defined or set up. I was going to, and still could, implement a function where if int h via "%02d", h is > say 18 then search for the icon name from a night list. However the more elegant way would be to simply replace the "d" in the img name with "n" since the night icons only differ in that regard and are all the 6th character in (ex owm04d and owm04n are day and night for the same conditions). I am having trouble getting that to work however. Would appreciate any help
I made a few changes to the theme in order to get the weather icons to fit better in the message.
There can be an issue with multiple weather messages stacking up. The widget will show the correct information.... unless the user deletes the newest weather message first. Example: weather message with clear sky, and weather message with clouds. The weather message with clouds is the newest and the widget reflects that. When opening the message_chain the newest message comes up first. If the weather message with clouds is deleted first, the weather widget would revert back to clear sky.
I wanted to keep the actual weather message as it provides more information than the icon does. Many conditions resolve down to a few icons. It would be nice to discard an old weather message when a new one comes in, not have it in the message chain, and have it accessible by the weather widget. But I have also had issues with removing the message widget. I am pretty sure I could delete the weather message after it is received via the message delete call back and the above issue would no longer exist, but we would lose the actual weather txt info. Maybe I will look to incorporate those into the widget.