Subj : msg_area.grp_list.sub_list scan_ptr
To : Nightfox
From : Digital Man
Date : Sat Apr 27 2024 11:07 pm
Re: msg_area.grp_list.sub_list scan_ptr
By: Nightfox to Digital Man on Sat Apr 27 2024 10:35 pm
> Re: msg_area.grp_list.sub_list scan_ptr
> By: Digital Man to Nightfox on Sat Apr 27 2024 08:34 pm
>
> DM> 'scan_ptr' is the message number that represents their highest read
> DM> message number. Any messages with a higher number (higher than the
> DM> scan_ptr value) will be considered "new".
>
> So, the test that I did was this:
> I first created a new (temporary) user account. I logged in with that user
> account and then set the scan pointer for all sub-boards to the current date
> & time. I did a newscan using the stock Synchronet reader, and it scanned
> all sub-boards and said there were no new messages (which I think was
> expected, since I had set the newscan poniters to the current date & time).
> I then did a newscan with my DDMsgReader (which uses scan_ptr), and it
> started at the first sub-board and showed the first message in that
> sub-board. If scan_ptr is the user's highest read message number, I think
> that makes sense. But I'm wondering if there's anything in JS that points
> to the user's configured newscan pointer instead?
The "highest read message number" and "newscan ponter" are the same thing.
There is a "last read message" number (the "last_read" property of msg_area.sub[]), that's not the same thing.
I'll experiment here and be sure that msg_area.sub[].scan_ptr is behaving as expected, but I'm pretty sure other script authors (e.g. echicken) are using it successfully.
--
digital man (rob)
Rush quote #74:
A modern-day warrior mean, mean stride, today's Tom Sawyer, mean, mean pride
Norco, CA WX: 55.8�F, 69.0% humidity, 1 mph WNW wind, 0.00 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net
