We’ve had a lot of questions about who will be presenting this year. The official deadline for submitting presentations is April 30th, with a final announcement on May 15th. We didn’t want to make you wait to find out who is presenting until then, so we went through the submissions we have received so far and preapproved a handful.
Currently Approved Presentations
|Quentin Aldredge||More Advanced Smartphone-like UIs Using QControls||Do you want more advanced User Interfaces than you can normally get from LabVIEW? Maybe the user experience needs to be for a touch screen similar to common smartphone interfaces. I’ll show tricks to using the QControl Toolkit to create swipe, scroll, and selection via a touchscreen more intuitive.|
|Casey May||Bowzer the Browser and the AF Guild||One of the side effects of working with Actor Framework is that the complexity of the block diagram is often moved to the file system. While this helps makes applications more scalable and modular, one area where it falls short is API/Message discoverability and navigation. Navigating the project to find the capabilities of each actor can be an exercise in frustration, especially for newer developers. The Bowzer the Browser aims to address some of these issues with the help of the Actor Framework Guild.|
|Darren Nattinger||Ludicrous Ways to Fix Broken LabVIEW Code||I worked for over 18 years in LabVIEW R&D as a feature developer. Two years ago I moved into NI’s Tech Support department to help mentor junior engineers and build their LabVIEW experience. In that time I have seen a lot of compiler errors, app builder failures, crashes… and most of the time, users will settle for any hack, kludge, or workaround just to get usable code. In this presentation I’m going to share a number of the ridiculous ways I’ve managed to get broken code running. Kinda like a fire extinguisher… you hope you never need to use it, but if you do, you’re glad it’s there.|
|Enrique Noe Arias||Improving the developer experience of DQMH Projects, a new ‘Generic DQMH API Tester-Launcher’||DQMH 6.1 comes with a new scripting API, I’m working on a new ‘Generic DQMH API Tester-Launcher’ using these new scripting tools, this development can scan all the DQMH modules on your project including the ones under dependencies, know some details of each module, launch the real API tester of the DQMH module selected, can trigger some of the default request events, the main purpose is to have a starting point when developing DQMH projects and help the developer to not lose the context by reducing the browsing of the project explorer.|
|Katya Prince||Introduction to Image Analysis||NI used to present an introduction to DAQ talk that covered the topics: Acquire – Analyze – Display. This talk will be a high level introduction to similar steps of Image Acquisition. It will cover Acquisition with cameras and lighting using a demo of MAX. Next, it will cover Processing and Analysis with a demo of Vision Builder. Finally, it will cover Display and some of the quirks and non-intuitive features of Image Processing.|
|Allen C Smith||Maps, Sets, DVRs, and Classes: A Practical Exercise||Collections – maps and sets – were added, without much fanfare, in LabVIEW 2019. These highly useful constructs are still new to many LabVIEW users. In this presentation, we will explore what maps and sets are and how you can use them to solve routine data management challenges. As a practical example, we will use maps, sets, and some additional LabVIEW features together to identify groups of objects that share common search tags.|
Got an idea?
This is just what we’ve approved so far. If you have an idea, it’s not too late. Use the button below to submit an idea before April 30.
If you want to check out all these presentations make sure you get your tickets before they sell out!