Subj : goated
To   : mark lewis
From : Richard Menedetter
Date : Sun Apr 07 2019 14:51:34

Hi mark!

07 Apr 2019 06:28, from mark lewis -> Richard Menedetter:


 ml>  On 2019 Apr 07 09:56:38, you wrote to me:

 ml>>> the problem seems to be that when RM reads a message addressed
 ml>>> to him, it should be marked as received... when he switches to
 ml>>> the other reader using the same message base files, that same
 ml>>> message is not marked received...
 RM>> Correct ... except all messages not only those addressed to me.
 ml> OH! then they are not ""marked received""... that's with the received
 ml> attribute bit in the message header and only if the name matches the
 ml> user's name... i got confused with your use of the phrase "marked
 ml> received" or "marked read"... messages aren't marked read or received
 ml> in general...

Let me rephrase.

1 READ
2 READ <- LASTREAD POINTER
3 UNREAD
4 UNREAD

If I read them in golded all will be marked read, and the lastread pointer will point to the last message (4).
If I read them in goated, it will updated the lasterad pointer, but the messages are still shown as unread.

1 READ
2 READ
3 UNREAD
4 UNREAD <- LASTREAD POINTER

So the unread pointer is updated, but the messages in the JAM base are not marked as read.
(and show up in a different color, as golded sees them as unread)

 ml> right... so the problem does appear to be something with the last/high
 ml> read pointers

No, the lastread pointer is updated correctly.

 ml> seems to have been done properly... i'm assuming that you do only have
 ml> 328 (or whatever that number was) messages in the area in question?
 ml> now i'm curious about that JLR data again and which of the two
 ml> programs was the last one used which would have written those counters
 ml> to the file...

The JLR file is fine.

CU, Ricsi

.... If you really want to be depressed, weigh yourself in grams.
--- GoldED+/LNX
 * Origin: If ignornace is bliss, you ought to be ecstatic. (2:310/31)

.