LabVIEW
How to disable LabVIEW checks the Grammar/Eddit Error Automatically function
I think it is kind of funny/ironic that you want to disable spell checking, but you spelled "edit" wrong in your messages.
You say your code is above 60M. What does that mean? Is it MB, megabytes? I don't tend to write super large projects, but 60 MB worth of VI's seems like an unusually large number to me.
Actually, I don't think I've seen spellchecking within LabVIEW, and almost certainly not grammar checking. Where do you find it if you want to change the setting manually?
I'm just guessing here that you want to explain that you have a project that loads lots of VIs and a change in a VI can make LabVIEW seem to freeze for some time before you can continue. I have seen this in large projects, where changes to a VI can take 10-20 sec to finish, which is quite annoying. What you can do is to split up your project into smaller parts so not everything is loaded at the same time. You can also load the VIs from outside the project environment, which will make the freeze-time for editing go away (along with some other annoyances for large projects).
It sounds like the OP has a super-mega-VI that is so large that any little change causes a recompile that takes up to ten minutes to compile. If this the case, OP... STOP!!! The answer isn't to disable some feature or option. The answer is to refactor your code right now, before it becomes corrupted and you lose everything. (Well, hopefully, you've been committing to your software repository regularly... right?)
The huge wait time is LabVIEW having a nervous breakdown in the background. Break the VI up into smaller chunks (subVIs).
Personally, I wonder how it is that developers who obviously understand coding best practices tend to abandon all all such practices when it comes to LabVIEW.
- Like putting everything in one humongous VI instead of breaking it up into subVIs, which are analogous to functions in a text-based language. You should make subVIs for exactly the same reasons you would make a function in a text-based language. (There are other, LabVIEW-specific reasons for doing this, but those are beyond the scope of my rant... err... discussion.)
- Or like creating massive spaghetti code with crooked, overlapping, backwards-running wires going behind structures - analogous to using random indents in a text language, making it impossible for a human to read.
- Or (more subtly) using the "Run Continuously" button instead of making a loop. I know some text-based language IDE has an analogous button to run code in loops. That's not the normal way to run code there; why should it be here?
Just a few "head-scratchers" that I've seen.
@API wrote:
Dear bill, Yes，we save the project per day for safety, and we have packaged many many modules as a subvi too, but, the whole project file size is huge. not a main vi is 60Mb.
That is worrisome, because that just sounds like normal LabVIEW development. Do you have a lot of data stored in the front panel as default data? That could make it super-slow to do stuff.
