#216 g UI crash on raspberry

[GewoonGijs]

@WouterJD I tested it yesterday evening, and it worked like a charm. Had a nice workout on Strava :)

[WouterJD]

@GewoonGijs now you've put me on the CallAfter() track; I also noted that the UI works better.

The data-fields op top of the SpeedMeters did not always refresh and all I knew to do is the code in
https://github.com/WouterJD/FortiusANT/blob/%23216-GUI-crash-on-raspberry/pythoncode/FortiusAntGui.py#L846
adding an alternating dot or comma to force refresh.
This already proves to be unnecesary; thanks!

Perhaps you can answer the question why self.panel.Refresh() is required to keep the data-fields visible.
The fields are more stable but still flickering a bit.

Perhaps it's related to the drawing actions in OnPaint().

Your suggestions are appreciated

[GewoonGijs]

Hi Wouter, I just looked in to it, and i think the problem is that the TextCtrl's are on top of the SpeedMeter controls. As is explained here http://wxpython-users.1045709.n5.nabble.com/wxPanels-and-Raise-td2316013.html wxPython has nog proper way to handle two controls that are placed on top of each other. I think the proper way to solve this is to place the textCtrl's below the SpeedMeter gauges. Maybe you can make the SpeedMeter a little less hig, and create som space for the text Ctrl's.

The self.panel.Refresh() works, because the complete panel is painted from scratch every cycle I think.

[WouterJD]

Thanks. I keep it asis then - no big issue.
The callafter() is already a hughe improvement👍