Hello g00r00!

I noticed that when listing files, and a user has ASCII, Mystic appears not to automatically use (force usage of) "Normal" type file listings instead of "Full" screen type file listings. I.e. it will not ignore user setting #17.

This is in contrast to the message editor type (user setting #15) and the message reader type (user setting #20), where Mystic appears to automatically use "Line" editor and "Normal" message reader, regardless of those settings, when a user has ASCII.

Perhaps an easy fix?

Thanks in advance!

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/05 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

I noticed that when listing files, and a user has ASCII, Mystic appears not to automatically use (force usage of) "Normal" type file listings instead of "Full" screen type file listings. I.e. it will not ignore
user setting #17.

It does fallback to to the non-full listing when ASCII mode is enabled and I just tested it on my BBS successfully.

How are you listing files? There must be more to it then that!

... Users come in two types: Those who have lost data, and those who will.

--- Mystic BBS v1.12 A47 2021/07/31 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 07 Aug 2021, g00r00 said the following...

I noticed that when listing files, and a user has ASCII, Mystic appea not to automatically use (force usage of) "Normal" type file listings instead of "Full" screen type file listings. I.e. it will not ignore user setting #17.

It does fallback to to the non-full listing when ASCII mode is enabled
and I just tested it on my BBS successfully.

How are you listing files? There must be more to it then that!

With the latest build the fallback for the file listing appears to work fine. I'll let you know if this problem re-surfaces. :)

Thanks!

Best regards
Zip

--- Mystic BBS v1.12 A47 2021/08/07 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)