Leaderboard

I have taken a few moments to re-factor LVSpeak and get it ready for the masses. For those of you who haven't heard me rant on about talking to LV I'll take a moment to give you a backstory. Back when LV scripting was unveiled in ~LV 7.0, I realized that we could merge the Microsoft Speech to Text API and LV scripting to aid us all in the process of coding. The idea sat idle until QuickDrop came out in LV8.6, and I couldn't not do it. Now, w/ the aid of this package, some rusty nails and the Microsoft Speech SDK, you can command LV with your voice w/ things like... [DISCLAIMER] This is not foolproof code. BUT I use it on a daily basis (actually I refuse to program w/out it turned on) Directions: Download the Microsoft Speech SDK 5.1 and install it Download and install the attached package to this post. Restart LV and now in your 'Tools' menu, you should see Enable LVSpeak. After you click it you will see two windows now floating whenever LV is active (untill you restart). The commands that it accepts currently are shown in the image above. [NOTE] They do not all work on both FP and BD. ex Alignment commands only work on the BD. [NOTE] This does not include integration w/ Quick Drop (although I would expect it to be added soon) I would recommend starting out w/ Saying things like 'V I Properties' ----------(both FP and BD) 'Align Left'----------------(on the BD) 'Graph Pallette'----------(on a FP graph) To stop the programs, simply say "LabVIEW Speak Stop" 'LVSpeak Engine' simply sets up the link between LV and the MS Speech API 'Quick Edit' is the engine that does the editing (This is where the fun happens)

Not sure how typecast is implement in LabVIEW. However in other languages (such is C) typecast is actually an operator, not a function. Using typecast just tells the compiler that the data in the memory location for variable x should be interpreted ('re-cast') as being of datatype y. That is, there is no function call at runtime associated with performing a typecast. However, I suspect the flatten to string primitive does do some low-level data interpretation / copying and may of some computational overhead. Swap bytes sounds like something the CPU instruction set would implement directly so I can imagine that this would be significant by comparison. Mostly speculation but I hope that helps. ~Dan