symbolCompletion

var symbolCompletion [(0|1)]

Examples:

"var symbolCompletion 1": Enable symbol completion in the top-level command reader.

This variable controls whether you can ask Swat to complete a symbol for you while you're typing a command. Completion is currently very slow and resource-intensive, so you probably don't want to enable it.

Even when symbolCompletion is 0, file-name, variable-name, and command- name completion are always enabled, using the keys described below.
When completion is enabled, three keys cause the interpreter to take the text immediately before the cursor and look for all symbols that begin with those characters. The keys are:

Ctrl+D: Produces a list of all possible matches to the prefix.
Escape: Completes the command as best possible. If the characters typed so far could be the prefix for more than one command, Swat will fill in as many characters as possible.
Ctrl+]: Cycles through the list of possible symbols, in alphabetical order.

sym-default

sym-default [<name>]

Examples:

"sym-default motif": Make swat look for any unknown symbols in the patient named "motif" once all other usual places have been searched.

Specifies an additional place to search for symbols when all the usual places have been searched to no avail.

The named patient need not have been loaded yet when you execute this command.
A typical use of this is to make whatever program you're working on be the sym-default in your .swat file so you don't need to worry about whether it's the current one, or reachable from the current one, when the machine stops and you want to examine the patient's state.
If you don't give a name, you'll be returned the name of the current sym-default.

sysfiles

sysfiles

Examples:

"sysfiles": Print out all open files from dos's system file table.

Normally SFT entries that aren't in-use aren't printed. If you give the optional argument "all", however, all SFT entries, including those that aren't in-use, will be printed.

See Also: geosfiles, sftwalk, fwalk.

systemobj

systemobj

Examples:

"gentree [systemobj]": print the generic tree starting at the system's root
"pobject [systemobj]": print the system object

Prints out the address of the uiSystemObj, which is the top level of the generic tree.

This command is normally used with gentree as shown above to print out the whole generic tree starting from the top.

See Also: gentree, impliedgrab.

target

target [<object>]

Examples:

"target": print target hierarchy from the system object down
"target -i": print target hierarchy from implied grab down
"target ^l4e10h:20h": print target hierarchy from ^l4e10h:20h down
"target [content]": print target hierarchy from content under mouse.

Prints the target hierarchy below an object.

If no argument is specified, the system object is used.
The special object flags may be used to specify <object>. For a list of these flags, see pobject.
Remember that the object you start from may have the target within its part of the hierarchy, but still not have the target because something in a different part of the tree has it.
The variable "printNamesInObjTrees" can be used to print out the actual app-defined labels for the objects, instead of the class, where available.

This variable defaults to false.

See Also: focus, model, mouse, keyboard, pobject.

targetobj

targetobj

Examples:

"targetobj": return object with target
"pobj [targetobj]": do a pobject on the target object (equivalent to "pobj -t").

Returns the object with the target.

See Also: target, focus, focusobj, modelobj.

tbrk

tbrk <addr> <condition>*
tbrk del <tbrk>+
tbrk list
tbrk cond <tbrk> <condition>*
tbrk count <tbrk>
tbrk reset <tbrk>
tbrk address <tbrk>

Examples:

"tbrk ObjCallMethodTable": Count the number of times ObjCallMethodTable() is called.
"tbrk count 2": Find the number of times tally breakpoint number 2 was hit.
"tbrk reset 2": Reset the counter for tbrk number 2 to 0.
"tbrk list": Print a list of the set tally breakpoints and their current counts.

This command manipulates breakpoints that tally the number of times they are hit without stopping execution of the machine--the breakpoint is noted and the machine is immediately continued. Such a breakpoint allows for real-time performance analysis, which is nice.

If you specify one or more <condition> arguments when setting the tally breakpoint, only those stops that meet the conditions will be counted.
The condition argument is exactly as defined by the "brk" command, q.v..
When you've set a tally breakpoint, you will be returned a token of the form "tbrk<n>", where <n> is some number. You use this token, or just the <n>, if you're not a program, wherever <tbrk> appears in the Usage description, above.
There are a limited number of tally breakpoints supported by the stub. You'll know when you've set too many.
"tbrk address" returns the address at which the tbrk was set, as a symbolic address expression.

See Also: brk, cbrk.

tcl-debug

tcl-debug top 
tcl-debug next <tcl-frame>
tcl-debug prev <tcl-frame>
tcl-debug args <tcl-frame>
tcl-debug getf <tcl-frame>
tcl-debug setf <tcl-frame> <flags>
tcl-debug eval <tcl-frame> <expr>
tcl-debug complete <tcl-frame>
tcl-debug next-call

Examples:

"var f [tcl-debug top]": Sets $f to be the frame at which the debugger was entered.
"var f [tcl-debug next $f]": Retrieves the next frame down (away from the top) the Tcl call stack from $f.

This provides access to the internals of the Tcl interpreter for the Tcl debugger (which is written in Tcl, not C). It will not function except after the debugger has been entered.

See Also: debug.

GEOS SDK TechDocs |

stream ... | Next:

text-fixup ...