https://gitlab.synchro.net/main/sbbs/-/commit/1da4cafe85bb0111db9c6cd7
Modified Files:
src/sbbs3/js_bbs.cpp sbbs.h
Log Message:
Introduce sbbs_t::sync() method that does what the old SYNC/ASYNC macros do

But... as rightful member of sbbs_t, thus useful from other scopes.

Should get rid of all use of SYNC/ASYNC now then.
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/fcffcae318514a7d45b23d5d
Modified Files:
src/sbbs3/js_bbs.cpp sbbs.h
Log Message:
Make JS bbs.msg_number and smb_curmsg writable

These 2 properties, specifically, could be made writable since
1. smb_t.curmsg is a special element owned by the application, not smblib
2. a special sbbs_t.current_msg_number property could be created/used to
underlie the bbs.msg_number when there's no open message base (by sbbs).

This might be all that's needed to resolve issue #793

The other bbs.msg_* and bbs.smb_* properties are not so easily made writable, so hopefully that's not desired.
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net