BoardInput QML Type

The mouse on a Board: wire pads, select and drag parts, operate, erase, tap a wire. More...

• List of all members, including inherited members

Properties

• board : Board
• dragSlop : real
• flow : var
• gated : bool
• grid : var
• grid \brief A \l GridMode; Alt inverts it for one drag. Optional. : var
• hands : var
• hands \brief The \l InstrumentBelt; asked second. Optional. : var
• hint : string
• hintKeys : var
• hoverActuator : bool
• hoverActuatorIdle : bool
• nav : var
• nav \brief The \c OrbitInput3D; asked first about every press. : var
• stage : var
• stage \brief The \l LabStage3D, for \c worldAt. : var
• view : var
• view \brief The View3D the stage projects through. : var

Signals

• interacted()
• operate(int id)

Methods

• void cancelAll()
• void clickAt(real x, real y, int mods)
• void dragFrom(real x1, real y1, real x2, real y2, int mods)
• bool granted(var hit)
• void moveAt(real mx, real my, int mods, bool isDown)
• void pressAt(real mx, real my, int button, int mods)
• void releaseAt()
• var worldAt(real mx, real my)

Detailed Description

The whole left-button gesture of a build lab, and the rule it lives by: the left button is always the board's. Navigation never competes for it - the camera (nav) is asked first and with its default buttons the answer for the left button is always no; then the hand (hands): an instrument out means the click is the instrument's. Only then is the press the board's, and what it does depends on what Board::hitAt found:

• nothing - clears the selection (and a dangling wire, unless erasing);
• with the eraser on - removes the wire or the part, at once;
• a wire - taps it: a junction is dropped there and the wire splits, so a branch can start anywhere;
• a terminal - starts a wire, or ends the dangling one;
• an actuator - selects the part first, operates it on the second click (operate fires on release, so a press that turns into a camera drag flips nothing);
• a body - selects and starts a drag.

With a flow wired, that whole list is conditional: while a lesson runs the board is the flow's, and only what the running task named answers at all.

The gesture lives in named functions (pressAt, moveAt, releaseAt, clickAt, dragFrom) rather than in the signal handlers, so a flow, a test or an agent can perform the SAME drag a hand does - the inspector can synthesize a click but not a drag. A right click walks back one step (hand, dangling wire, eraser, selection - in that order); a right drag still turns the view and cancels nothing.

BoardInput {
    id: boardMouse
    board: board; nav: nav; hands: hands; stage: stage; view: view3d; grid: grid
    flow: root.currentFlow                 // while it runs, the board is its
    onOperate: (id) => root.toggleSwitch(id)
}

See also Board, OrbitInput3D, InstrumentBelt, GridMode, and Flow.

Property Documentation

Signal Documentation

Method Documentation