Requires: Base Development System
Class: Splitter Events
Type: Filter
Generated when you click the mouse button on a splitter bar.
| Name | Description | ||
|---|---|---|---|
| Source | Source of the event. LabVIEW UI refers to any built-in user interface event.
| ||
| Type | Type of event that occurred, such as Mouse Down, Value Change, Timeout, and so on. | ||
| Time | Value of the millisecond timer when the event occurred. | ||
| CtlRef | Reference to the control on which the event occurred. | ||
| Coords | Coordinates of the mouse at the location of the mouse click at the time of the event. Coordinates are relative to the upper left corner of the front panel. | ||
| Button | Value that corresponds to which mouse button the user clicked. Left mouse button is 1, right mouse button is 2. Operating systems might assign higher numbers if you have a mouse with more than two buttons. For filter events, you can modify the data returned by this event data field. | ||
| Mods | Cluster of Booleans that contain platform-independent modifiers. LabVIEW returns all platform-dependent modifiers in the PlatMods event data field. For key events, this event returns a Boolean indicating if the event occurred on the numeric keypad. For mouse events, this event returns a Boolean indicating if the event was a double-click. For both events, a Boolean is returned if the platform-independent menu key, such as <Ctrl> on Windows or <Command> on macOS, was pressed when the event occurred. For filter events, you can modify the data returned by this event data field. | ||
| PlatMods | Cluster of Booleans that contain platform-dependent modifiers. Specifies if platform-dependent keys, such as <Ctrl>, <Shift>, <Alt>, <Command>, and <Option> were held down when the event was triggered. For filter events, you can modify the data returned by this event data field. A key can be both a Mod and PlatMod. For example, <Ctrl> is the platform-independent menu key on Windows, but you also can use it in platform-dependent programming. | ||
| Discard? | Allows you to prevent LabVIEW from processing the event, bypassing the behavior normally triggered by that event. The default is FALSE. |