inputManagerobject | input.t[65] |
Superclass Tree | Property Summary | Method Summary | Property Details | Method Details |
inputManager : PostRestoreObject
inputManager
PostRestoreObject
ModuleExecObject
object
inProgressDefObj
inputEventInProgress
inputLineInProgress
noInputTimeout
Inherited from PostRestoreObject
:
restoreCode
Inherited from ModuleExecObject
:
execAfterMe
execBeforeMe
hasInitialized_
isDoingExec_
isExecuted_
cancelInputInProgress
execute
getEvent
getEventOrKey
getInputDialog
getInputFile
getInputLine
getInputLineExt
getKey
inputBegin
inputEventBegin
inputEventEnd
inputLineBegin
inputLineEnd
pauseForMore
Inherited from ModuleExecObject
:
_execute
classExec
inProgressDefObj | input.t[577] |
inputEventInProgress | input.t[580] |
inputLineInProgress | input.t[574] |
noInputTimeout | input.t[599] |
Note that if this value is nil, it means only that we've never seen an InEvtNoTimeout return code from inputLineEvent - it does NOT mean that timeouts are supported locally.
We assume that the input functions are uniform in their treatment of timeouts; that is, we assume that if inputLineTimeout supports timeout, then so does inputEvent, and that if one doesn't support timeout, the other won't either.
cancelInputInProgress (reset) | input.t[414] |
If 'reset' is true, we'll clear any input state saved from the interrupted in-progress editing session; otherwise, we'll retain the saved editing state for restoration on the next input.
This MUST be called before calling tadsSay(). Games should generally never call tadsSay() directly (call the library function say() instead), so in most cases authors will not need to worry about calling this on output.
This MUST ALSO be called before performing any keyboard input. Callers using inputManager methods for keyboard operations won't have to worry about this, because the inputManager methods call this routine when necessary.
execute ( ) OVERRIDDEN | input.t[543] |
getEvent (promptFunc?) | input.t[291] |
getEventOrKey (promptFunc, keyOnly) | input.t[306] |
Note that this routine is not generally called directly; callers should usually call the convenience routines getKey() or getEvent(), as needed.
getInputDialog (icon, prompt, buttons, defaultButton, cancelButton) | input.t[257] |
getInputFile (prompt, dialogType, fileType, flags) | input.t[243] |
getInputLine (promptFunc?) | input.t[79] |
promptFunc can either be a callback function to invoke to display the prompt, or a single-quoted string containing the prompt. Of course, the caller can simply display the prompt before calling this routine rather than passing in a prompt callback, if desired.
If we're in HTML mode, this will switch into the 'tads-input' font while reading the line, so this routine should be used wherever possible rather than calling inputLine() or inputLineTimeout() directly.
getInputLineExt (defObj) | input.t[91] |
getKey (promptFunc?) | input.t[272] |
inputBegin (promptFunc) | input.t[525] |
inputEventBegin (promptFunc) | input.t[441] |
inputEventEnd ( ) | input.t[456] |
inputLineBegin (defObj) | input.t[470] |
inputLineEnd ( ) | input.t[496] |
pauseForMore ( ) | input.t[234] |