Location: Mopac C, 1S13 @ NI headquarters 11500 North MoPac Expressway, Austin TX
Date: Tuesday, November 17, 2015
Time: 6:00 PM Central Time
Duration: ~ 2 hours
Format: presentation plus group discussion
Food: We will need an accurate headcount, so please register here. We will need National Instruments members to register as well, for that, you will get an internal invitation. If you are not sure if you are in that internal list and want to be, please let Fabiola know (fabiola@delacor.com). If you are attending remotely, there is no need to register, just let us know where you are joining us from when you log in.
Meeting Description
"Channel Wires a.k.a Jeff's wire"
Channels ship as part of LabVIEW 2015, but they are not officially released. A big reason for this is that NI is not sure if they are a good idea in their current form and would like to get feedback from early adopters. Stephen will show us how to enable them and give us an introduction to this powerful hidden feature in LabVIEW 2015. [Edit from Stephen: LV2015 is so last season! I will be doing demos from LV2016, which incorporates feedback we've already gotten from customers and a all the development work that has happened since the time management said "Guys, you gotta stop adding to 2015 so we can ship."]
With LabVIEW 2015, you can now add plug-ins to the editor environment to adjust the right-click menus of the panel and diagram. Darren will show us how to write effective plug-ins and explore the plug-ins that do not ship with LabVIEW that you may wish to download.
Thanks to Sixclear for sponsoring remote connection. If you can't make it to NI for the meeting, join us remotely via screenshare and audio conferencing!
Please mute your phones during presentations to help minimize background noise for others joined on the conference line. To ask questions or supply comments simply pipe up or use the chat window (available when you join the screenshare) which we'll monitor throughout.
What's your objective in presenting Jeff's wire, Stephen? If you present in 2016, you'll provide little value to those wanting to use the feature in current or near-term projects. If you want to gather more feedback, wouldn't we provide more useful feedback having actually used it instead of just watching demos?
You can still use it in 2015 and provide us more feedback. By showing 2016, I can make you aware of topics that we've already gotten feedback on and have locked in for the next release vs things that are still open to conversation. There's also some amount of doubt in the community about the utility of the wire, and with 2016, I can show more demos that we've written... I can't show those in 2015 because of the extensive changes we've made.
