Currently when the kv4p HT app is restarted, any APRS messages in the "text chat" view are cleared out.
We should instead persist all APRS messages, and store them to the local DB. I'm currently only using the local DB for settings, so we'll need some new DB objects for APRS stuff. And the UI handling for the text chat view will need to be more sophisticated, representing whatever is in that DB, and when we receive APRS we won't add it to the UI but instead the DB (a truer MVC approach).
Need to limit how many APRS messages are rendered in the scrollback buffer so it doesn't make the phone laggy after years of use.
VanceVagell
commented
11 hours ago
Currently when the kv4p HT app is restarted, any APRS messages in the "text chat" view are cleared out.
We should instead persist all APRS messages, and store them to the local DB. I'm currently only using the local DB for settings, so we'll need some new DB objects for APRS stuff. And the UI handling for the text chat view will need to be more sophisticated, representing whatever is in that DB, and when we receive APRS we won't add it to the UI but instead the DB (a truer MVC approach).
Need to limit how many APRS messages are rendered in the scrollback buffer so it doesn't make the phone laggy after years of use.