I've committed my in-progress code on this to a new branch (dbl-tap-for-next-active) because I can only get it partially working. Jumping to the next active chat is easy, but the buffer never seems to be marked as read, so double-tapping again just re-loads the same buffer. It's not until you double-tap for a THIRD time that the buffer is marked as read, so that a FOURTH double-tap takes you elsewhere (and other clients are notified).
I can't figure out why this is happening or how to fix it, so this issue is on hold for a while.
I've committed my in-progress code on this to a new branch (dbl-tap-for-next-active) because I can only get it partially working. Jumping to the next active chat is easy, but the buffer never seems to be marked as read, so double-tapping again just re-loads the same buffer. It's not until you double-tap for a THIRD time that the buffer is marked as read, so that a FOURTH double-tap takes you elsewhere (and other clients are notified).
I can't figure out why this is happening or how to fix it, so this issue is on hold for a while.