Professional Documents
Culture Documents
http://labviewartisan.blogspot.in/2012/05/spell-checking-in-labview.html
But enough of the sales pitch (we've got other people around here for that)...here are some of the reasons our current spell checking solution is less than ideal: Lack of integration - If you want to spell check your code, currently you have to run a separate tool (VI Analyzer) in order to see the results of the misspellings, as opposed to the standard way of just getting a red wavy underline of misspelled words as you type. Also, to add a word to the custom dictionary, you have to do that through the VI Analyzer as well, as opposed to simply being able to right-click a word and add it to the custom dictionary. Although I suppose it wouldn't be too tough to write a Quick Drop Keyboard Shortcut or a JKIRCF plugin to enable a UI gesture to do this as you sift through your VI Analyzer results. English only - The VI Analyzer Toolkit is not localized, so we only provide English dictionaries. Maintenance difficulty - Ok, this one is kind of selfish, but it's up to me, as the VI Analyzer Toolkit owner, to keep track of LabVIEW features that add different text fields to a VI so I can add the scripting code to the Spell Check test to get the text out of those fields. In fact, I discovered recently a feature that was added two releases ago that I have yet to add Spell Check support for... :\ Despite these deficiencies, I've spoken to multiple developers who use the Spell Check test regularly because it's the best tool they have for identifying and fixing spelling mistakes in their VIs. So with this blog post, I have a few questions to ask: 1. Do you use the VI Analyzer Spell Check test? If so, how has the experience been? 2. Do you think it's a feature that would be worth significant investment for LabVIEW R&D to integrate better into the LabVIEW editor? 3. Are there any words you've found flagged by the Spell Check test that you think should be added to our standard dictionary or our technical dictionary? Even if you've never used the Spell Check test, or even thought about spell checking in LabVIEW before, your feedback is welcome! Posted by Darren Nattinger at 2:24 PM
7 comments:
1 of 3
12-Dec-13 12:16 PM
http://labviewartisan.blogspot.in/2012/05/spell-checking-in-labview.html
crelf May 11, 2012 at 3:50 PM Nice "other people" link :D Reply
Steve Bird May 21, 2012 at 2:58 PM Do you use the VI Analyzer Spell Check test? No. My spell checker is between my ears. Do you think it's a feature that would be worth significant investment for LabVIEW R&D Gosh, no. Like "Diagram Cleanup", this is an solution in search of a problem. Spend your R&D money on fixing the problems with LabVIEW (I've found 3 confirmed bugs so far this year, that make charts useless in my app), not on this fluff. Reply
John Lokanis June 5, 2012 at 2:04 PM I think a live spell checker would be a big improvement. This seems like an ubiquitous feature in most modern applications these days. Heck, I just used the one in Chrome to spell check 'ubiquitous' in this post! Also, I think the dictionary you use in VI Analyzer needs some improvement. I got this message today: This free label contains the misspelled word "incremented". Really? And don't try telling me that is not a common word in the LabVIEW world... Reply Replies Darren Nattinger June 5, 2012 at 2:59 PM
Thanks for the feedback, John. As I mention in the blog post, 'lack of integration' is the biggest problem we have with spell checking in LabVIEW today. In the meantime, I'll make sure to get 'incremented' added to the VI Analyzer spell check list. :) Reply
Maciej Antonik July 24, 2012 at 5:19 AM Hi, I haven't tried, but I hear that some people use general Windows spellcheckers like http://tinyspell.numerit.com/ or similar. Any experience with that? Reply
MLR266 August 19, 2012 at 2:54 PM I did not know there was a method for checking spelling in LV and i will start using it. I would love to see an integrated spell checker in LV. I know for me personally it would encourage better documentation of my code. Currently, I tend to type into MS Word and then copy/paste into LV. This means i need to make the note long enough to make it worth the copy/paste operation, or simple enough that i know i have not screwed it up. Reply
Jonathon Green August 30, 2012 at 3:08 AM This would be great both in IDE and Run Time. Kudos this idea: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/LabVIEW-Spell-CheckFor-String-Control-in-Run-Time/idi-p/1661466
2 of 3
12-Dec-13 12:16 PM
http://labviewartisan.blogspot.in/2012/05/spell-checking-in-labview.html
3 of 3
12-Dec-13 12:16 PM