display totals for mAh, KMs, mins

[wowi69]

added to display: total mAh used, total distance flown (in km), total airborne time (mm:ss)

couldnt find osdconfig.txt, so these are the lines to be added:

define TOTAL_AMPS true // set to false if you dont want to see this

define TOTAL_AMPS_POS_X 19

define TOTAL_AMPS_POS_Y 15

define TOTAL_AMPS_SCALE 1

define TOTAL_DIST true // set to false if you dont want to see this

define TOTAL_DIST_POS_X 6

define TOTAL_DIST_POS_Y 19

define TOTAL_DIST_SCALE 0.8

define TOTAL_TIME true // set to false if you dont want to see this

define TOTAL_TIME_POS_X 19

define TOTAL_TIME_POS_Y 19

define TOTAL_TIME_SCALE 0.8

[wowi69]

https://github.com/wowi69/EZ-WifiBroadcast/blob/develop/_additions_to_osdconfig.txt https://github.com/wowi69/EZ-WifiBroadcast/blob/develop/wifibroadcast_osd/render.c https://github.com/wowi69/EZ-WifiBroadcast/blob/develop/wifibroadcast_osd/render.h

hope everything is clear, to display totals just replace render.c and render.h and add the extra lines in osdconfig.txt (all based on v1.6RC6)

[bortek]

This will have to wait until we update the repos with the files from the img file.

[Yes21]

This Pull Request will have to be merged with this one, before 1.7 integration. Thanks

[bortek]

@RespawnDespair I merged your other PR https://github.com/bortek/EZ-WifiBroadcast/pull/158 . This one now has a lot more changes. Do you think we need to merge this one cause most of the changes you are doing on your side will have the latest stuff already in it?

[Yes21]

@wowi69 Your PR has been transferred here. It's now ready to be merged.

[rodizio1]

There is one problem with this: It's not guaranteed that the OSD keeps running, whenever wbc_status is called to display a status message (for example when plugging a smartphone for USB tethering or connecting to the Wifi Hotspot) the OSD gets killed and then re-started after.

This would also reset those counters (and is the reason I haven't integrated a flight timer yet).

I haven't really thought it through yet, but I guess a better solution to the quick&dirty wbc_status would be to move this functionality into the OSD, i.e. implement some means to send messages to the OSD that the OSD then displays.