ReachProblemclass | query.t[1038]

An object describing a reach problem; such objects are used by the Query object to communicate problems with one object touching another to the touchObj PreCondition (see also precond.t). ReachProblem objects are normally created dynamicallty as required, although it is usually one of the subclasses of ReachProblem that it used.

`class ReachProblem : object`

Superclass Tree (in declaration order)

`ReachProblem`
`object`

Subclass Tree

`ReachProblem`
`ReachProblemBlocker`
`ReachProblemCheckReach`
`ReachProblemDistance`
`ReachProblemReachOut`
`ReachProblemRemote`
`ReachProblemVerifyReach`

Global Objects

(none)

Summary of Properties

`target_`

Summary of Methods

`check construct verify`

Properties

`target_` | `query.t[1066]`

The object we're trying to reach

Methods

`check (allowImplicit)` | `query.t[1058]`

The check() method of a ReachProblem should check whether the target object can be reached by the source object. If allowImplicit is true the check method may attempt an implicit action to bring the target object within reach.

Return true if the target object is within reach, and nil otherwise.

Note that the check() method of a ReachProblem will normally be called from the checkPreCondition() method of touchObj.

`construct (target)` | `query.t[1060]`

no description available

`verify ( )` | `query.t[1045]`

Problems which reaching an object that occur at the verify stage and which might affect the choice of object. If the verify() method of a ReachProblem object wishes to rule out an action it should do so using illogical(), inaccessible() or other such verification macros.

Adv3Lite Library Reference Manual
Generated on 12/09/2014 from adv3Lite version 1.4