DDMsgReader: Ctrl-C is now supported for message searches to abort the search.
1 unresolved thread
Compare changes
+ 28
− 7
@@ -117,6 +117,9 @@
@@ -222,8 +225,8 @@ var ansiterm = require("ansiterm_lib.js", 'expand_ctrl_a');
@@ -1005,6 +1008,7 @@ function DigDistMsgReader(pSubBoardCode, pScriptArgs)
@@ -1934,6 +1938,15 @@ function DigDistMsgReader_SearchMessages(pSearchModeStr, pSubBoardCode, pScanSco
@@ -1956,6 +1969,11 @@ function DigDistMsgReader_SearchMessages(pSearchModeStr, pSubBoardCode, pScanSco
@@ -2623,14 +2641,16 @@ function DigDistMsgReader_MessageAreaScan(pScanCfgOpt, pScanMode, pScanScopeChar
@@ -7616,7 +7636,7 @@ function DigDistMsgReader_WriteMsgListScreenTopHeader()
@@ -8532,6 +8552,7 @@ function DigDistMsgReader_ReadConfigFile()
The proper way to check for user aborting about (e.g. hitting Ctrl-C) is to check the
console.aborted
property.The only reason this wouldn't work for your script is because you're putting 'C' (CTRL-C) in the ctrl-key passthrough list. Do you have another use for the Ctrl-C key? If not, then I would recommend letting Synchronet handle Ctrl-C input and use
console.aborted
to see if/when a user has aborted.