mkinney

For example, the `ls_secs` should show somewhere in the tool tip, label or somewhere.

It might be helpful to add info about OS, how user installed m-flasher, version of m-flasher (kind of like a `support` info)

Go thru fields.json description and add validation for various fields

3

There should be some validations added to settings. If so, write a generic function in util.py and call it in the form. For example, if a valid range is from...

Change out QMessageBox calls

5

A QMessageBox.information or .warning will not show a title in the WindowTitle on mac. For example: but the window title does work on a normal QDialog on mac: So, we...

add capability to download from CI builds

2

It would be nice to be able to add to an advanced option (or something) to allow a user to download builds from CI. for example: https://github.com/meshtastic/Meshtastic-device/actions/runs/1789823637 has a built.zip...

improve the look of the input forms in Settings

1

The tabs are not really visible as tabs. The input fields have a distinct look and feel that could be improved. Anyone want to take a stab at changing the...

Code coverage has really suffered during the addition of the Settings screens.

Spin thru the `print` statements and either comment out or remove them. They were mainly used for dev. Not sure what info to leave for debugging issues if user has...

Do different validations

1

Leverage Docker and/or vagrant for validation of various OSes

raspberry pi arm64 research

4

Can we get `meshtastic-flasher` working on a raspberry pi? PySide6 nor PySide2 is not available. See https://bugreports.qt.io/browse/PYSIDE-802?focusedCommentId=418104&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel