Drag Over Event
Installed With: Full Development System
Class: Control Events
Type: Notify
Generated when there is a drag and drop operation pending, as the mouse moves over a control.
Use this event if the drop target allows or disallows dropping on it depending on where the mouse is located. For example, you can use this event if you only want to allow a user to drop in a graph plot area and nowhere else on the graph.
You may want to use the Drag Enter event instead if the mouse location on the target is inconsequential. Because the Drag Over event fires continuously as it checks to see if the drag is accepted, as opposed to the Drag Enter event which fires once, you also may want to use the Drag Enter event if you do not need to specify a location on the target.
Event Data Fields
| 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 location of the mouse click at the time the event occurs. Coordinates are relative to the drop target's owning pane origin, excluding clusters. | ||
| 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 Mac OS, 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. | ||
| Available Data Names | Array of unique names of data types available during this drag and drop operation. Use this array to determine if a data type is available that the drop target can accept | ||
| Accepted? | Reports to the drag source the action that the drop target would take if the drop occurred at this moment. TRUE, if the target would accept the drop, FALSE otherwise. |