For the user to interact with the 3D model your application needs to respond to various input events that might be coming from the mouse, the keyboard or a touch device. While you are free to handle user input yourself and make calls into the Web Viewer API in response to them we provide the concept of "Operators" for this purpose. An operator is a hook into the user input event loop with a predefined structure to respond to user input in a sensible way.
The Web Viewer has a set of pre-built, standard operators for various user interactions like camera manipulation, selection or inserting markup, but you can also write your own operators with completely custom functionality.
Creating Custom Operators
Every event handler receives an event object related to its type of event. For mouse events, an example would be the type of MouseInputEvent, for Touch events the type is TouchInputEvent. The event object has various member functions to retrieve the mouse location, button status, and other relevant information.
For a list of all Event objects please see the Reference Manual.
Operators can be as simple as the one above that turn an object transparent while the mouse is pressed, or they can be much more complex and have multiple stages like an operator that performs a measurement operation and then positions the resulting markup based on user input. It is up to you to decide how complex you want to make the interaction that is encapsulated by a single operator.
Registering an Operator
Custom operators must be registered with the OperatorManager. Registering the operator makes it available but does not activate it.
Registering an operator returns an identifier which you can then use to activate the operator later. Each custom operator has a unique handle.
Activating an Operator
There are two ways to activate a registered operator. The first one is to simply push it on the Operator "stack".
The OperatorManager maintains a stack of operators that are all active at the same time and receive events based on their position in the stack with the operator pushed on the stack last getting to "see" the events first. When starting the Web Viewer this is what the operator stack looks like:
When using the push function your custom operator will be added to the end of the stack (position 6 in this case) and be first in line to receive events. You can then "pop" it from the stack at any time with the OperatorManager.pop() function.
You can also "replace" an existing operator on the stack at a specific position with OperatorManager.set():
In this case, the default select operator is replaced by your custom operator at position 1 in the stack. If you want to remove an operator from the stack without replacing it, you can call the OperatorManager.remove() function. Be aware that this function will modify the position of all operators above it in the stack.
If you prefer to start over and define your operator stack from scratch, you can use the OperatorManager.clear() function which completely empties the operator stack.
To retrieve a particular Operator object (to call functions on it, change settings, etc.) you can use the OperatorManager.getOperator() function. There can only be one object of a given type on the Operator stack at a time, so you only need to pass the relevant OperatorId to this function.
All Operator events (e.g onMouseUp(), onMouseDown()) are sequentially propagated to all operators on the stack starting with the operator highest on the stack. This is so that multiple operators can be active at the same time and effectively run in parallel. Because of this, an operator must be carefully designed to not interfere with the behavior of other operators or the application must ensure that the operator is the only one active.
If an operator handles an event of a given type it often needs to "consume" the event meaning it needs to stop it from propagating down to the operators lower in the stack. In the case of the NavCubeOperator, for example, this is because the Operator might have determined that the NavCube element has been clicked on. In that case, it makes no sense to send the mouse messages also to the Orbit operator which would result in an unexpected camera movement. Another example might be an operator only "interested" mouse events but letting all other event types (e.g. keyboard events) pass through.
To consume an event simply call setHandled() on the event object in the function that processes the event. If this function is called all the operators lower in the stack will not see the event but instead, receive a stopInteraction() event indicating that their current action (e.g. orbiting the camera, moving the cutting plane, etc) should be canceled. You should make sure that your custom operator also handles the stopInteraction() event.
For a more advanced Operator Example please consult the Advanced Operator Concepts section in the Building A Basic Application tutorial.
The Web Viewer supports several predefined operators in various categories. All those operators are available with fully readable source-code. We encourage you to browse through the source code to understand some of the more advanced design patterns when writing operator code.
Activating a Predefined Operator
As with the custom operators you need to be mindful of how an activated operator interacts with other operators already on the stack. For example, if you want to use one of the walk operators you should not just push it to the top of the stack but instead, replace the existing camera-related operator (Navigate in the default configuration) with it. If in doubt it is best to experiment to see how the predefined operators interact with each other and define your operator stack accordingly.
The built-in operators fall into a few major categories:
Please see the reference manual for more information on each Operator Category. Some of them will also be discussed throughout this Programming Guide.