Current implementation of Conversation/Social threading in Windows client will mark any new received messages as read if:

1: part of existing conversation
2: Message window is open to this conversation
3: left unattended for perioud of time

This is problematic as many users leave active messages open when away from computer, only to find newly received messages are easily missed as the client has already marked them as read.

Client should not mark messages in thread as ready unless

A: New message bubble is clicked or hovered by mouse pointer
or
B: Conversation is actively scrolled

by: Rodney W. | over a year ago | Windows Client

Comments

• This newest version is just ridiculous. I never really liked Groupwise, but this tops all. Who thought that using chat features will help? You tried to merge Messenger into Groupwise by using threads like speech bubbles. Thing is, I need more than just that to reply or modify features in my reply (like the list of people who receives it). How can I get back to the older version look?? Now it is a mess. At least you should have given a choice instead of deciding it for the user.

  by: Gabi C. | over a year ago

• Gabi, you can simply disable the Enable conversion threading in Tools>Options>Environment>General
  This is settable by gw admin.
  
  In defense of this new feature, some of us actually like the idea. It just needs some more fine tuning.

  by: Rodney W. | over a year ago