• Default 'snap to' bahaviour

    From Avon@21:1/101 to g00r00 on Wednesday, February 27, 2019 20:45:34

    Hi there

    [snip]

    N Area Description Total New Yours Last Post ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
    NEW Automated roBOT Posts 25,006 7 0 27 Feb 2019
    NEW General Chat 54,587 29 2 26 Feb 2019
    NEW InterBBS Data 3,941 14 0 26 Feb 2019
    NEW Magicka BBS Support/Dev 499 8 0 27 Feb 2019
    BBS Support/Dev 5,798 0 0 25 Feb 2019
    Cryptographics 629 0 0 10 Jan 2019
    Mystic BBS Support/Dev 13,329 0 0 27 Feb 2019
    Netmail (fsxNet) 2,962 0 0 26 Feb 2019

    Fidonet ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
    NEW ALLFIX File Announce 1,010 10 0 27 Feb 2019

    [snip]

    In the above example if I am reading posts in the Magicka base and read everything, when I exit back out to this index view the reader will snap to
    the next NEW base below the last base read.. so it jumps to the ALLFIX File Announce..

    What I think would be preferable would be for the reader to keep it's focus
    on any remaining NEW bases in the group that is currently being read.

    This will avoid needless scrolling upwards using the arrow keys to place
    focus on unread bases in the group being read. Do you think a
    snap_focus_group = true or similar could be added to the behavior of the
    reader and into the .ini file for folks to enable/disable?

    Best, Paul

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

    --- Mystic BBS v1.12 A43 2019/02/23 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From g00r00@21:1/108 to Avon on Wednesday, February 27, 2019 03:30:10
    What I think would be preferable would be for the reader to keep it's focus on any remaining NEW bases in the group that is currently being read.

    This will avoid needless scrolling upwards using the arrow keys to place focus on unread bases in the group being read. Do you think a snap_focus_group = true or similar could be added to the behavior of the reader and into the .ini file for folks to enable/disable?

    Probably an easier change might be to jump to the "first new" base when it snaps instead of the next base after the one you just read. But I am not sure how I like that either, so maybe I could add it so it always tries to snap to the group before then moving on down the list, as you describe.

    I don't know that I need to make it an option I think maybe it should
    just always work that way.

    --- Mystic BBS v1.12 A43 2019/02/26 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Avon@21:1/101 to g00r00 on Wednesday, February 27, 2019 21:44:48
    On 27 Feb 2019 at 02:30a, g00r00 pondered and said...

    Probably an easier change might be to jump to the "first new" base when
    it snaps instead of the next base after the one you just read. But I am not sure how I like that either, so maybe I could add it so it always tries to snap to the group before then moving on down the list, as you describe.

    I don't know that I need to make it an option I think maybe it should
    just always work that way.

    Yep whatever works for you, but thanks, it would be helpful vs having to keep arrowing up if I choose a base that is last in the group of NEW bases within
    a group. :)

    Best, Paul

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

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