Event Handling: Difference between revisions

Latest revision as of 21:14, 17 June 2020

See also: Functions Palette/Programming/Structures/Event Structure

Overview

The Event Structure in LabVIEW executes code in response to a software interrupt.

The most common use-case is to respond to user interaction with a user-interface through typical input (keyboard, mouse, touch), but it can also be used to respond to events that are programmatically generated elsewhere in the software.

One event structure can be registered to respond to multiple events. Each event can execute a unique frame of the structure. A single frame can be registered to handle multiple events.

There are best-practices when using an Event Structure related to when/how it blocks and when the data flow 'reads' the user-interface element that generated the event.

Using Events to Respond to User Interface Interactions

Using Events to Respond to User Defined Events

Revision as of 07:00, 16 May 2020 view source Logmanoriginal (talk \| contribs) Bureaucrats 3,469 edits m Add see also for the event structure ← Older edit		Latest revision as of 21:14, 17 June 2020 view source Q (talk \| contribs) Bureaucrats, Administrators, Widget editors 22,507 edits Category reorg
Line 13:		Line 13:

	== Using Events to Respond to User Defined Events ==		== Using Events to Respond to User Defined Events ==

			[[Category:Programming Elements]]