Martin Mathes

Thanks for the great work and great documentation to go with it! I think I found a bug/feature request with `bar` widgets: If you limit the range to say 0-100,...

Looks like we have miles of space there? So for DE: "Farbe Akku fast leer" "Farbe Akku mittel" "Farbe Akku voll" If there is more space maybe insert a "bei"...

DE ``` #define TR_DATE_TIME_WIDGET "Datum & Uhrzeit" #define TR_RADIO_INFO_WIDGET "Fernst. Info" #define TR_LOW_BATT_COLOR "Farbe Akku fast leer" #define TR_MID_BATT_COLOR "Farbe Akku mittel" #define TR_HIGH_BATT_COLOR "Farbe Akku voll" ```

That mesh background feels a bit too much like 2000 era design to me. Isn't the trend towards more flat design? I would even prefer a completely black/grey background TBH....

Maybe dumb question: this is _not_ SRXL protocol but something else they just use for communication between satellite and main receiver?

I wonder whether we should add more complexity on top of the channel5 special handling, or try and get rid of it completely? If I got the conversations in previous...

Same here > ➜ ~ flatpak run com.solvespace.SolveSpace Sorry, only UTF-8 locales are supported. ➜ ~ localectl System Locale: LANG=en_US.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 VC Keymap: us X11 Layout:...

I remember from a past life that if I patch this locale check out and rebuild the flatpak myself, SolveSpace runs just fine. What is this check supposed to prevent?

DE ``` #define TR_VUSBJOYSTICK_CH_SIM "Quer","Höhe","Seite","Gas","Beschl.","Bremsen","Lenkung","Dpad" #define TR_VUSBJOYSTICK_CIRC_COUTOUT "kein","X-Y, Z-rX","X-Y, rX-rY","X-Y, Z-rZ" ``` How many chars do we have space for? I assumed 5 based on "Steer"

@feiticeir0 with nautilus/gnome, it works for me via `dav:///`, no username or password required.