HyperMesh, HyperView, HyperGraph 2D, HyperGraph 3D, and MotionView now support the following SpaceBall or SpaceMouse devices from 3Dconnexion: SpaceNavigator, SpacePilot, SpaceExplorer, and SpaceTraveler.
Before running HyperWorks, be sure that current drivers are installed for your device. HyperWorks will automatically detect and enable the use of the SpaceBall/SpaceMouse once the device is connected and working properly.
The 6 degrees-of-freedom input on the SpaceMouse devices require no special configuration prior to using it within HyperWorks, however the 3Dconnexion control panel may be used to adjust the sensitivity of the device, as well as how the axes respond to input.
Buttons on SpaceMouse devices are programmable, and some user customization is required in order to optimize the use of these buttons. Each button can be programmed using the 3Dconnexion control panel to generate a keyboard key press event, a button event, or to change one of the 3Dconnexion control panel settings. For example: button 1 on the SpaceBall/SpaceMouse device can be programmed to generate the HyperView keyboard shortcut 'M' (to toggle the mesh line display), using the Custom Functions button on the 3Dconnexion control panel.
Note: The HyperWorks applications listed above will respond best to 3Dconnexion buttons when they are configured to emit button events. |
A sample configuration for the SpacePilot (on the Windows platform) is shown below:
3Dconnexion Control Panel - SpacePilot sample button configuration (on the Windows platform)
The following table summarizes how the HyperWorks applications will respond to button events from 3Dconnexion devices:
Button Event Number |
Function |
---|---|
1 |
Top View |
2 |
Left View |
3 |
Right View |
4 |
Front View |
5 |
Fit View |
6 |
ISO View |
7-10 |
View Memory Buttons |
11-16 |
User defined TCL callbacks |
17-29 |
These buttons cannot be customized within HyperWorks applications because they are supported across various platforms (Windows, LINUX, etc.). |
Note On SpaceExplorer and SpacePilot devices, the T, L, R, F, and Fit buttons should be configured for button events 1, 2, 3, 4, and 5 respectively.
The View Memory Buttons on the SpaceBall/SpaceMouse devices work similar to the M1, M2, and R1, R2 buttons on the View Controls dialog (located in the lower right corner of the HyperWorks panels).
|
SpaceMouse button events 11 - 16 are programmed to call user defined TCL callback handlers. These allow you to customize the SpaceMouse functionality to meet your needs. Three Session object methods are provided to allow programmability of 3Dconnexion buttons:
|
The following example demonstrates how to program button event 11 to toggle animation on and off.
proc ::FlipAnim { state } {
# Only respond to button events, which occurs when state == "True" if {$state == "False"} { return; }
hwi OpenStack; set t [lindex [split [expr rand()] .] end];
catch { hwi GetSessionHandle sess$t; sess$t GetProjectHandle proj$t; proj$t GetPageHandle page$t [proj$t GetActivePage ];
if {"false" == [page$t IsAnimating] } { page$t StartAnimation; } else { page$t StopAnimation; }
} hwi CloseStack;
}
set t [lindex [split [expr rand()] .] end]; hwi GetSessionHandle sess$t set buttonID [sess$t GetSpaceballButtonMin]; sess$t RegisterSpaceballCallback $buttonID ::FlipAnim; sess$t ReleaseHandle;
|
HyperMesh Mouse Graphic Controls