I don't have the most exact debugging information on this, yet. However, there is a definite issue with the comparisons for what rooms have new messages in findNew() vs. scanSub()/readNew(). This can be evidenced by jumping to a room before performing a new message scan. At all times, when initiating a scan, the current room will have [at least] the last message read upon new scan. I believe (at this point) that the number of messages seen as 'new' depends on some unknown factor within the pointers of the current room, as it seems to vary between at least one and two messages that are displayed.
There needs to be some decent code thrown in for (modularly) comparing the different pointers' values; this would probably be a perfect opportunity to try to get that working for proper debugging.
dgets
commented
8 years ago
I don't have the most exact debugging information on this, yet. However, there is a definite issue with the comparisons for what rooms have new messages in
findNew()vs.scanSub()/readNew(). This can be evidenced by jumping to a room before performing a new message scan. At all times, when initiating a scan, the current room will have [at least] the last message read upon new scan. I believe (at this point) that the number of messages seen as 'new' depends on some unknown factor within the pointers of the current room, as it seems to vary between at least one and two messages that are displayed.There needs to be some decent code thrown in for (modularly) comparing the different pointers' values; this would probably be a perfect opportunity to try to get that working for proper debugging.