You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using 2.2.9 I received a notification which I pressed . The message, which was several days newer than the previous one, appeared at the top of the thread instead of as usual the bottom. The messages from this person are unencrypted for some reason. My reply appears just under this.
The text was updated successfully, but these errors were encountered:
public static final String DEFAULT_SORT_ORDER = "timestamp";
Sort order is indeed by timestamp (Android ListView will reverse it), but I wonder if it's the right thing to do. I could order by message id: it's an atomic sequence number, so it will always order by date of creation in the local database.
What do you think?
It seems to work correctly (sqlite sequence number will restart when overflowed, this means something like an unsigned 64-bit number, which is really some lifetimes worth of messages).
I don't remember why I've used timestamp instead of _id in the first place...
Using 2.2.9 I received a notification which I pressed . The message, which was several days newer than the previous one, appeared at the top of the thread instead of as usual the bottom. The messages from this person are unencrypted for some reason. My reply appears just under this.
The text was updated successfully, but these errors were encountered: