mirror of
https://github.com/oxen-io/session-ios.git
synced 2023-12-13 21:30:14 +01:00
e08fa4bcec
When we send the nth message, we retain the footer for the n-1th message until the nth message is successfully sent. 1. leave the footer on the n-1th message 2. draw the nth message with the "..." footer 3. update the nth message with the "sent" footer and hide the footer for the n-1th message In the normal case this all happens very quickly, which results in some unpleasant flicker every time you send a message. The concession here is that we'll only print the n-1th footer if the outgoing message *fails*. So until we implement a design more like Android's double-check for sent/delivery, the user will not be able to distinguish between a sent and delivered message *while* their message is outgoing. In my opinion the lack of jank in the normal case makes the app supercedes this use case. // FREEBIE |
||
|---|---|---|
| .. | ||
| call | ||
| contact | ||
| crypto | ||
| environment | ||
| Jobs | ||
| Models | ||
| network | ||
| Observers | ||
| Profiles | ||
| Storyboard | ||
| UserInterface | ||
| util | ||
| ViewControllers | ||
| views | ||
| AppDelegate.h | ||
| AppDelegate.m | ||
| MessageSender+Promise.swift | ||
| Signal-Bridging-Header.h | ||
| UIApplication+OWS.swift | ||
| UIColor+OWS.h | ||
| UIColor+OWS.m | ||
| UIDevice+featureSupport.swift | ||
| UIStoryboard+OWS.swift | ||
| UIView+OWS.h | ||
| UIView+OWS.m | ||