• Events System

    From Avon@21:1/101 to g00r00 on Saturday, November 11, 2017 09:20:25
    This post should confirm 1/101 has moved up to 11/09

    I've noticed a possible issue in the events system in MIS2

    If you set an event to inactive e.g. semaphore event, then start MIS2, then
    run mystic -cfg and make the event active again.... MIS2 will not rescan the config data to pick up the change.

    This is a departure from MIS that would seemingly rescan key config settings every 60 secs and events would be added or removed from the list of active events...

    Just something to check :)

    Best, Paul

    --- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From g00r00@21:1/108 to Avon on Friday, November 10, 2017 19:36:24
    If you set an event to inactive e.g. semaphore event, then start MIS2, then run mystic -cfg and make the event active again.... MIS2 will not rescan the config data to pick up the change.

    Yes, that is intentional. There will be a CTRL-R to manually restart the event system when on its tab, and an option to automatically detect changes and reload them.

    Or if I don't like how that works I'll just make it automatic without an option for similar to how MIS works. The difference between the two event systems means that when you "refresh" the event data, you'll lose any "pending" events that you currently have, as the entire system will be refreshed. MIS1 didn't have pending events, they were just lost if they landed while another event was going.

    --- Mystic BBS v1.12 A36 2017/11/10 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Avon@21:1/101 to g00r00 on Saturday, November 11, 2017 17:21:12
    On 11/10/17, g00r00 pondered and said...

    Yes, that is intentional. There will be a CTRL-R to manually restart
    the event system when on its tab, and an option to automatically detect changes and reload them.

    Or if I don't like how that works I'll just make it automatic without an option for similar to how MIS works. The difference between the two
    event systems means that when you "refresh" the event data, you'll lose any "pending" events that you currently have, as the entire system will
    be refreshed. MIS1 didn't have pending events, they were just lost if they landed while another event was going.

    OK thanks for the background info and explanation. :)

    --- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)