VI analyzer has a built in spell check.
By default, it will spell-check analyze the VI name. If you happen to use VI names with dash, underscore or whitespace between the words, you're fine. If you happen to use CamelCase for your VI names (MySpecialFileName.vi), every one of your VI names will be flagged as misspelled. Bummer.
There's 4 ways around this:
1) Stop doing spellcheck in VI analyzer (not that great -- I want to fix my spelling problems)
2) Stop using CamelCase for my VI names (I could, but that's a lot of work to change them all, and I like not having spaces in my file names)
3) Add every file name (or parts of the file name that are separated by dash/underscore/whitespace) to the custom VIanalyzer dictionary, and then pass this dictionary around to everyone else that works on this library. (bummer that it doesn't have an option to reside with the vianalyzer .cfg file like any other configuration -- I could make a custom dictionary for just that cfg, but then I need to pass around a few files to be part of the .cfg, and I can't merge multiple spellcheck dictionaries). Updating the custom dictionary is pretty annoying every time I add a new VI.
4) go to the configuration screen for VI Analyzer spell check and uncheck "VI Information" flag. Then it stops spellchecking the file name. But it also stops spellchecking the VI description, and I really want to spellcheck the description (since that stuff goes on my documentation that is seen by other users/customers).
So how about swizzling the configuration flags somehow for VI Analyzer spell checker to allow me to disable spellcheck for the VI name but still spell check the VI description?
