On 10 Feb 2019, g00r00 said the following...

Also, for those of you using the current "index reader" I would start to look into using the new index reader as I am going to make the cut over sometime in the near future, probably for A43. So the old one will go away.

Howdy, I tried the next index reader today and had two problems:

1) Private Mail (local mail) is setup as default (which I think the param is "Forced" mail scan) and I've noticed if I view that base, I cannot get out of it unless I "finish" reading the last message. (I try to get out by pressing ESC).

With the new index reader, I couldnt "get out" of reading that base unless I went to the last message and then went to go "next" which prompts if you if
you want to post a new message - responding no gets me out.

2) Netmail - I have my netmail base with no "g" acl, ie: I use s20 - so "netmail" shows up in all bases. With the new index reader, if I pressed "enter" to go into it and then came out, pressing "enter" again doesnt get me into it a second time. The only way to get into it is to leave the message index reader and come back, OR go to the netmail mail from another message
base (since it shows up on multiple bases).

Thought you might like to know...

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)

On 11 Feb 2019, deon said the following...

1) Private Mail (local mail) is setup as default (which I think the
param is "Forced" mail scan) and I've noticed if I view that base, I cannot get out of it unless I "finish" reading the last message. (I try
to get out by pressing ESC).

BTW: I tried this in the older index reader AND by selecting that message
base with a normal read (not via the index reader).

Even though all messages are "read", I cannot get out (pressing ESC) unless I go to the last message and attempt to proceed past it - and since there are
no more, I'm prompted to post. Responding no to post gets me out...

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)

1) Private Mail (local mail) is setup as default (which I think the
param is "Forced" mail scan) and I've noticed if I view that base, I cannot get out of it unless I "finish" reading the last message. (I try
to get out by pressing ESC).

If Private Mail is set to Forced then its doing what it should do. But by default it should not be configured as Forced. I'll do a quick fresh install and if for some reason the default is Forced I'll get it fixed up. And if not I'll try to reproduce this.

2) Netmail - I have my netmail base with no "g" acl, ie: I use s20 - so "netmail" shows up in all bases. With the new index reader, if I pressed "enter" to go into it and then came out, pressing "enter" again doesnt
get me into it a second time. The only way to get into it is to leave
the message index reader and come back, OR go to the netmail mail from another message base (since it shows up on multiple bases).

I will look into this right away! Thank you very much for testing out the
new index reader! This is obviously why these pre-alphas exist and its great to see people helping to test!

Thought you might like to know...

Very much so, thank you!

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 13 Feb 2019, g00r00 said the following...

If Private Mail is set to Forced then its doing what it should do. But

Agree - but if all the mail is "read", it shouldnt force me to read it again
to get out :)

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)

If Private Mail is set to Forced then its doing what it should do. B

Agree - but if all the mail is "read", it shouldnt force me to read it again to get out :)

I am curious what you're trying to accomplish by setting a base to forced that you don't want users to be forced to read? Maybe there is some way I could make it determine if there are new or unread messages and allow exiting otherwise, I'll have to see how easy that would be.

The feature itself mimics one from Renegade BBS and it was typically used for things like BBS Annoucements. The idea being that you'd post your news there and then setup the BBS to newscan that base during login with the forced flag, so users were forced to read all new BBS annoucement messages. I agree it doesn't translate well to the index reader, if you choose to have forced bases listed there.

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 13 Feb 2019, g00r00 said the following...

I am curious what you're trying to accomplish by setting a base to
forced that you don't want users to be forced to read? Maybe there is

Actually, I dont recall setting it forced, and if I did I was playing.

Your use case is the right one though. If I wanted to post a bulletin/message that users should read, then setting it to force will enable that.

However, after I have read it, if I read that message area again (and there
are no new messages), I shouldnt have to read all messages (or get out via
the last message).

This problem is not limited to the index reader. If I choose that message
area and select read messages - I'm stuck in that area, and the only way
out is to jump to the last message...

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)

Actually, I dont recall setting it forced, and if I did I was playing.

Your use case is the right one though. If I wanted to post a bulletin/message that users should read, then setting it to force will enable that.

I was able to make the change so that you can now stop reading a forced base if you have already read the last message! I was worried it'd take a bit of code change for that but it turned out to be a pretty quick fix.

However, after I have read it, if I read that message area again (and there are no new messages), I shouldnt have to read all messages (or get out via the last message).

Oh I agree I wasn't trying to deny that :)

I was just curious as to why anyone would turn that on if they didn't want to use it in sort of a "system news" type of way. Sometimes people come up with some interesting ways to do things that I don't think about, so I often will pick brains a little bit.

This problem is not limited to the index reader. If I choose that message area and select read messages - I'm stuck in that area, and the only way out is to jump to the last message...

Yep, it was everywhere but that should be fixed now in this next build, along with the file moving stuff hopefully. I've tried to go through all of the code but I think there are like half a million lines of code so I might have missed something.

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 14 Feb 2019 at 08:25p, g00r00 pondered and said...

I was able to make the change so that you can now stop reading a forced base if you have already read the last message! I was worried it'd take
a bit of code change for that but it turned out to be a pretty quick fix.

This is a good catch... I think this may have bedeviled me also. Will test on next build.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/10 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

This is a good catch... I think this may have bedeviled me also. Will
test on next build.

Great! And I have finished other goodies related to echomail in the next
build too that you may like! :)

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 15 Feb 2019 at 03:51a, g00r00 pondered and said...

Great! And I have finished other goodies related to echomail in the next build too that you may like! :)

Cool we're all being rather spoiled right now and Christmas was over a month ago :) My mind has turned to all things global... I'll just have to wait and see. Or I wonder if it's those features you created a while back but have
been inactive until now?? I'd better get some zzz... darn it, now I'll be pondering tonight when I should be sleeping :)

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/10 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Cool we're all being rather spoiled right now and Christmas was over a month ago :) My mind has turned to all things global... I'll just have

Sadly, you're going to be disappointed :( But I have started on that too.

to wait and see. Or I wonder if it's those features you created a while back but have been inactive until now?? I'd better get some zzz... darn

Bingo! And I tossed in two other similar features too in the message and
file bases because I can't give all the action to just the hubs ;)

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 14 Feb 2019, g00r00 said the following...

Yep, it was everywhere but that should be fixed now in this next build, along with the file moving stuff hopefully. I've tried to go through
all of the code but I think there are like half a million lines of code
so I might have missed something.

You da man!

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)