LLB opening bug

[zirya]

Hello!

When i try to open LLB's Top-Level VI without using LLB Manager in LabVIEW 8.5 (LabVIEW.ini has line useLLBManager=False) it opens but in a second an exception is shown and LabVIEW terminates. This method of opening LLBs worked perfectly on LabVIEW 8.0 and the LLB is not corrupted, because it opens just fine using LLB manager or "Open..." dialog in LabVIEW.

Does anyone know if there is a chance to get this working?

[parthabe]

Behaviour confirmed!

[Jennifer_R]

Hi zirya and Partha,

This was reported to R&D (# 4DOED73A) for investigation.  It is a known issue that LabVIEW 8.5 crashes when a VI in an LLB is opened and LLB Manager is disabled.  If you do not want to use the LLB Manager, you may be interested in the suggestions made in this thread.  The workarounds mentioned include creating a shortcut to LabVIEW that points to the VI and removing the VI from the LLB. 

Message Edited by Jennifer_R on 04-09-2008 07:08 PM

[parthabe]

Thank you, Jennifer.

[Travis_M.]

For those interested, the new bug ID for this issue is 67983.  We switched our bug report database to a new system and so the bug IDs changed.  The issues documented in the Known Issues List have both the legacy ID and the new ID for reference.

[JasonD_at_DL]

Could someone please tell me why the original method of double clicking a .llb file is now defaulted to open the Library Manager?

I develop code, carefully place all my VIs in a .llb, and assign the top level VIs to be to ones to AUTOMATICALLY open on launch - which to me means double clicking the .llb file.

There HAS to be a workaround to get it back to be the old way - right? I have to distribute code to numerous locations, to folks of limited skill sets, and now, rather than tell them to double click the file, I have to tell them to muck about in a Library Manager?

Come on! You're killing me with these senseless changes!

Could someone please suggest the proper way to produce my desired result (which btw is the way it was working for 10 years).
Have I become a LabVIEW coding dinosaur?

Thanks.
NI Folks - please contact me!

Jason

[Travis_M.]

With LabVIEW 8.5.1 you can use an ini key.  See KB 3F4EB2NY

[JasonD_at_DL]

Thanks Travis,
You definitely caught me on a bad day...

What I still find unfortunate is that for the 30-40 deployments I oversee, I now have to add a line to each LV .ini file.
I guess I would have appreciated it if the default behavior caused -no change-, but if I wished to --as you put it "open for easy viewing through the LLB manager by default" I could then do so.

I'm deeply concerned that there is a serious divide between how NI *thinks* LV is used and how it is *actually* used in the wild.

I'll be certain to be more pro-active in beta testing in the future.

Thanks

[Dennis_Knutson]

Would it not be much more efficient to distribute an exe instead of an llb? Do these people of 'limited skill sets' also need the ability to edit the program?

[JasonD_at_DL]

The .exe might be an option, but it'd be a tough sell due to contractual limitations and the remoteness of the deployment. There have been times when I've had to talk the user though a minor code tweak.

The other issue for me is the cross platform one. I'm literally deploying on XP, Mac, and Linux. So, for an .exe I'd have to compile for each.

I'll have to brush up on standalone deployment strategies.

Still, it's a workaround for something that was historically, always defaulted in a certain way, which leaves a bad taste...

Thanks!