LabVIEW Interfaces: Exploring Their Potential For Improving Our Code
summary
Claims that interfaces introduced in LabVIEW 2020 enable multiple inheritance and behavioral contracts, and that using them with the actor framework yields concrete patterns: default implementations relay messages up the actor tree, a scripting tool generates interfaces to replace heavy legacy classes, and a loggable interface centralizes event logging. Applied to a 7,500-VI codebase, replacing clusters with scripted interfaces stops intermittent build failures (keeps build time ~2–2.5 hours) and restores IDE responsiveness while preserving runtime behavior.
AI-written summary · about
chapters (10)
- 0:00LabVIEW fun tool
- 3:05Interfaces vs classes
- 6:15Actor framework basics
- 9:26Decoupling actors
- 12:17Complex actor hierarchies
- 15:29Sequencing tasks
- 17:17Refactoring legacy code
- 21:51Loggable interfaces
- 24:21Async callbacks
- 26:00Q&A
related talks
23mThe invisible mechanisms in your interfaces
42mProgrammers Don't Have to Be Bad Interface Designers
44mInteractive assistant: block the entire UI and make the user happier
25mA Common Design Language. Let Designers and Developers talk to each other
32mThe journey to interactive components
51mLet’s use IntelliJ as a game engine, just because we can
01h 03mEvolving compositional user interfaces
59mModern User Interfaces for C++