OK, I was feeling good about having everything on the MY COMPUTER side compile up to the host itself.
But the host itself is a disaster.
Is LV2017 really the unmitigated dog it appears to be?
Either I'm misunderstanding something very basic, or LabVIEW is flat out lying to me.
For example, while loading, it failed to find something, which was located in exactly the same place it's always been. When I pointed out where it was, exactly where it was expecting it, I get this:
le:![Crap1.png]( "Crap1.png")
LV just built this PPL not two minutes earlier, but now it's unreadable ? ? ?
WHY?
But that's a lie, because if I wade thru the loading process and then go and find the error, where it's missing, I can replace it from that exact same place, and it's OK. the library IS readable!
I gave up at 120 of those things. Why do I have to go and find them when the VI told you where they were and they're still there? ? ?
If you ignore everything and start replacing the "missing" things, here is a dialog .
Note that the library it complained about above is perfectly readable.
Also note that it is looking for something in exactly the place where it is, but cannot find it .
![Crap2.png]( "Crap2.png")
Most (all?) of these errors are in two PPLs, both compiled under the RT part of the project. I suspect that if I go and compile them under the MY COMPUTER, things will clear up.
I understand if I did something wrong, or if things changed that my project might not work anymore, LV should tell me what the problem is, and I'm fine.
But why tell me it cannot find something, when it actually shows me where it is?
Why tell me something is broken when you it was just built a moment ago?
Arrrgh
