Project messed up due to LVOOP

[Eugen_Graf]

Yes, I have had a VI (wich was not used in my project, but needs the Logger Class) in the project directory but not in the project list. Now I deleted this VI from the directory and mass compiled (without Project was loaded). I get no more errors in the mass compile log window.

But I get the same errors starting Executable.

Thank you for help, but the problem isn't solved yet.

Message Edited by Support on 12-01-2008 01:31 PM

[Eugen_Graf]

I unchecked the "Remove FP" option for these 4 VIs, now I get only one error - 2208

The Run Button in the Exe is broken.

Message Edited by Support on 12-01-2008 01:31 PM

[Eugen_Graf]

Nobody can help???

This error 2208 is not explained, what should I do now?

Message Edited by Support on 12-01-2008 01:31 PM

[Intaris]

It seems that Error 2208 has to do with LVOP items missing sub-VIs which are not explicitly linked to the class.

Have a look at http://forums.ni.com/ni/board/message?message.uid=622700 and http://forums.ni.com/ni/board/message?board.id=170&thread.id=305400.

Safari doesn't seem to want to allow me to use the "Insert Link" option.  Sorry.

Shane. 

Message Edited by Support on 12-01-2008 01:31 PM

[Andrey_Dmitriev]

Colleagues, there are definitively some bugs in LVOOP. For example, last week I have developed nice calsses hierarchy... I have added one more class, then methods, more calsses, and more methods... And then explosion happened when I reached approximately 10 classes:

This coming every time when I trying to open project. Something completely damaged. Well, I working under source control, taking working code back. But exactly the same happened one and half year ago with version 8.2. And now again. Now I using classes very "moderate". But development of the big object oriented project in LabVIEW is impossible. At least very dangerous- you should always stay prepared that you will loose your work.

Andrey.

Message Edited by Andrey Dmitriev on 11-24-2008 01:23 PM

Message Edited by Support on 12-01-2008 01:32 PM

[Eugen_Graf]

Ok, but how can I link VIs from my user-libraries to a class and why? I will only use some VIs from user lib in member VIs of a class. If I link VIs from user library to a class, than I will not be able to use them in an another class or project, because they will be locked by owner class.

Message Edited by Support on 12-01-2008 01:32 PM

[Intaris]

Have you tried to tell LV to explicitly include those VIs in the EXE which you are referencing within the classes?  It might be that LV doesn't follow all the links of dynamically-dispatched VIs.

Just a guess.

Shane. 

Message Edited by Support on 12-01-2008 01:32 PM

[Eugen_Graf]

Ok, I linked all VIs from PCAN library to the CAN Class now. But the problem stays.

All classes are included as  "Always Included"

 

 

Message Edited by Eugen Graf on 11-24-2008 07:11 AM

Message Edited by Support on 12-01-2008 01:33 PM

[Andrey_Dmitriev]

Hi, Eugen,

Probably Auto-populating folders is the problem? Try to replace these folders with virtual folders.

Another idea - try to define custom destination for every class.

Andrey.

Message Edited by Support on 12-01-2008 01:33 PM

[Eugen_Graf]

Yes, I defined one folder for each Class, but the problem wasn't away.

Than I put the DLL, which will be called by Library into the CAN-Folder and the problem isn't present now!

But now I have many folders with allthe VIs. It's not good, but for temporary solution ok.

 

 

Message Edited by Eugen Graf on 11-24-2008 07:35 AM

Message Edited by Support on 12-01-2008 01:33 PM