When using the options to read New Messages only, and skip to next area with new messages; I observe a skip of areas.
i.e.
Area 1
Area 2
Area 3
If I'm reading Area 1, and reach the end, and say yes to go to next area.
It starts with area 3 not area 2 as expected.
Have you seen this behavior ? Could be my setup but wanted to inquire.
When doing a scan to read new messages only, it will skip areas that don't have any new messages. Maybe thare are no new messages in area 2.
Nightfox
Amessyroom wrote to Nightfox <=-
Re: DDMsgReader - Message Area Skipped
By: Nightfox to Amessyroom on Sat Nov 16 2024 10:58 am
When doing a scan to read new messages only, it will skip areas that don't have any new messages. Maybe thare are no new messages in area 2.
https://gitlab.synchro.net/-/snippets/21
See if these screen shots explain it better. I read all messages, in
first area. Completed said yes goto next, and it went to the 3rd.
Amessyroom wrote to Nightfox <=-
Re: DDMsgReader - Message Area Skipped By: Nightfox to Amessyroom on Sat
Nov 16 2024 10:58 am
When doing a scan to read new messages only, it will skip areas that
don't have any new messages. Maybe thare are no new messages in area 2.
https://gitlab.synchro.net/-/snippets/21
See if these screen shots explain it better. I read all messages, in
first area. Completed said yes goto next, and it went to the 3rd.
Dude. Did you not read what he said above? The obvious answer is that there are NO NEW MESSAGES in Area 2. That's why it was skipped.
Also, neither of the two links you posted in that gitlab link work.
By: Nightfox to Amessyroom on Sat Nov 16 2024 10:58 amHere is new link, evidently gitlab doesn't make uploads public in snippets even when snippet is public. Don't know how to change that.
When doing a scan to read new messages only, it will skip areas that
don't have any new messages. Maybe thare are no new messages in area 2.
Nightfox
Dude. Did you not read what he said above? The obvious answer is that there are NO NEW MESSAGES in Area 2. That's why it was skipped.
The screen shots showed there were messages in area 2.
Here is new link, evidently gitlab doesn't make uploads public in snippets even when snippet is public. Don't know how to change that.
https://anonpaste.io/share/4fd67dbed0#53XLeH5NDVfIqge
will show the screen shots.
Here is new link, evidently gitlab doesn't make uploads public in snippets even when snippet is public. Don't know how to change that.
https://anonpaste.io/share/4fd67dbed0#53XLeH5NDVfIqge
will show the screen shots.
Re: Re: DDMsgReader - Message Area Skipped By: Errol Casey to Gamgee on Sun Nov 17 2024 10:09 am
Dude. Did you not read what he said above? The obvious answer is
that there are NO NEW MESSAGES in Area 2. That's why it was skipped.
The screen shots showed there were messages in area 2.
But are they *new* messages?
--
digital man (rob)
Re: DDMsgReader - Message Area SkippedTry #3
By: Amessyroom to Nightfox on Sun Nov 17 2024 11:08 am
Here is new link, evidently gitlab doesn't make uploads public in
snippets even when snippet is public. Don't know how to change that.
https://anonpaste.io/share/4fd67dbed0#53XLeH5NDVfIqge
will show the screen shots.
It says that screenshot does not exist or has been deleted/expired.
Nightfox
Here is link to my ddmsgreader user options you asked about also. It should be showing only new messages and areas.
https://toolazy.synchro.net/images/ddmsgreader_user_options.png
Re: DDMsgReader - Message Area Skipped
By: Amessyroom to Nightfox on Sun Nov 17 2024 11:08 am
I have seen instances where when scanning for new messages, an earlier sub-board will happen to get a new message while reading a later sub-board (due to a network exchange via QWK or FTN), so it would appear that it may have skipped that sub-board, but it's because it initially didn't have any new messages. I wonder if that's what's happening for you?
Sysop: | Kurt Hamm |
---|---|
Location: | Columbia, SC |
Users: | 7 |
Nodes: | 20 (0 / 20) |
Uptime: | 228:45:37 |
Calls: | 2,774 |
Calls today: | 2 |
Files: | 64 |
Messages: | 848,178 |