Commit graph

11 commits

Author SHA1 Message Date
geeksville
67d95039bf begin support for message status 2020-05-30 14:38:16 -07:00
geeksville
6e261fa35e don't let the user send empty messages 2020-05-15 11:55:32 -07:00
geeksville
5abb56ec3f a better fix for the problem of sending messages while device is asleep
Better just to Observe myId and wait for it to be !null
2020-04-21 20:48:44 -07:00
geeksville
2dd37e791d don't let users try to send texts if we haven't received our node ID
I wanted an and not an or ;-)

Based on the autobug and the great report inhttps://github.com/meshtastic/Meshtastic-esp32/issues/102

I think this should fix the crash described in the messages screen.
2020-04-21 20:29:34 -07:00
geeksville
fdd3b48364 don't let users try to send texts if we don't have a node id 2020-04-19 12:31:27 -07:00
geeksville
69e6b285c6 we now allow changing BLE connection to different meshtastic devices on the fly 2020-04-09 13:28:44 -07:00
geeksville
8c70d5f67d a few more strings 2020-04-09 11:27:42 -07:00
geeksville
5a90a06580 get ready for translations 2020-04-09 11:03:17 -07:00
geeksville
749103cd09 message sending kinda works again 2020-04-08 17:50:23 -07:00
geeksville
29f0435f18 message fragment kinda works 2020-04-08 17:12:39 -07:00
geeksville
e157bb0140 add beginnings of new messages tab 2020-04-08 16:49:27 -07:00