https://gitlab.synchro.net/main/sbbs/-/commit/8da6013947680646b77ef6ad
Modified Files:
exec/avatar_chooser.js ftn-setup.js exec/load/mouse_getkey.js tree.js exec/xtrn-setup.js xtrn/minesweeper/minesweeper.js
Log Message:
Use Synchronet's built-in mouse tracking supportSynchronet uses "extended normal" mouse reporting for mouse support(e.g. menu/display file clickable "hot spots"). Many of the JS scriptsthat predated Synchronet's own internal mouse support would send theirown mouse-reporting enablement and disablement ANSI sequences and theterminal could become out of sync with the expectations of the script(i.e. it would not necessarily disable the mouse modes that had beenset by SBBS before enabling its own preferred mode).And some scripts (e.g. Synchronet Minesweeper) use a mixture of Synchronethotspot support and direct mouse click coordinate reporting, so it was amess going between different mouse reporting modes at different times in thesame script.This all came to light as a result of the fix for issue #412: using mousebutton releases rather than presses to trigger a hotspot.So mouse_getkey() now has as a separate "release" property it sets in thereturn value. Right now its always the opposite of "press", but I can imaginesome mouse tracking modes where movement might be reported with neither abutton press nor release event.Anyway, Nelgin, give this a try and see if it resolves the issues you werereporting in IRC with avatar chooser mouse support.
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)