Overwriting of main.py file in Monocle device

[ironmanfpv]

Whenever Monocle runs NOA, any main.py code in Monocle gets cleared out by NOA. While it could be a feature that ensure robustness of the device under development and use, if a user uploads a main.py and in between that wants to use NOA, then NOA will wipe clean the main,py file and there is a need to repeatedly upload files into main.py.

Could something be done to mWhenever Monocle runs NOA, any main.py code in Monocle gets cleared out by NOA. While it could be a feature that ensure robustness of the device under development and use, if a user uploads a main.py and in between that wants to use NOA, then NOA will wipe clean the main,py file and there is a need to repeatedly upload files into main.py.

Could something be done to maintain robustness of the device and yet allow customisation and flexibility of use of device ?
For example, if a user wrote some code in main.py for a customised greeting splash screen, upon 1 use of Monocle with NOA, that greeting splash screen would be totally written over.

Also, if user develops a app on Monocle, upon using Monocle with NOA, that app might cease to be usable.aintain robustness of the device and yet allow customisation and flexibility of use of device ?
For example, if a user wrote some code in main.py for a customised greeting splash screen, upon 1 use of Monocle with NOA, that greeting splash screen would be totally written over.

Also, if user develops a app on Monocle, upon using Monocle with NOA, that app might cease to be usable.

[trzy]

This a tricky one because Noa is designed to run for extended periods of time as a background companion app on your phone and this requires Monocle use its main.py. There isn’t really any built in support for retaining and switching between multiple apps on Monocle and the model right now is that each companion app basically just pushes its script overwriting what was previously there.

It might be possible to download the previous main.py and then add an option to restore it from the mobile app but this would still require considerable manual intervention on the user’s part.