neo_zion
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by neo_zion
-
-
You can disconnect a VI from its owning library with the "disconnectFromLibrary" method.
As far as disconnecting all the typedefs from a library of VIs, I'm not aware of any way to do this without scripting.
The best way to do this would be to
1. open the library reference (I prefer to open a VI in the library, and use a "library" property node read.)
2. Invoke node on library "Get All Decedents" and get the Control VIs from this
3. Read the "VI Reference" in a for loop of the decedent results.
4. Set the "VI Control Type" property to control.
5. Save each VI with an invoke node save.
6. While you are at it get all the standard VIs and "disconnectFromLibrary" method.
7. Save standard VIs
8. Save the library.
That will disconnect all typedefs by saving them as a standard control instead of manually disconnecting them in each VI (that is a huge pain, I wouldn't even try.)
the disconnectFromLibrary method will take them all outside of the .lvlib as well.
Before you try any of this, make sure you back everything up, including the projects that use this library.
Additionally I would run your script from the same project instance as the one that you use these VIs in. Sometimes Labview gets confused otherwise when you reopen the project.
~Jon
Thanks a lot for your suggestion. I am able to disconnect the VI's from library. However I am not able to "Set the "VI Control Type" property to control" which is mentioned in your Step 4. I would really appreciate if you could modify the attached VI to incorporate the step 4 mentioned.
Thanks,
Neo
-
What is the specific reason you want to disconnect from the lvlib?
The lvlib can be included with the LLB like any other LabVIEW file.
However you should disconnect each VI from the owning lvlib, there might be a VI-server method for this, but I am not sure.
Ton
My customer doesn't want its dependency with lvlib files. He likes the old way of code distribution.
-
I have a set of drivers which I am trying to disconnect from *.lvlib file and distribute as *.llb file. But whenever I save it to a new distribution,it shows that all member files retains lvlib dependency,
- Is there any way to remove this lvlib dependency at single shot? -I have around 350 files, hence opening and disconnecting will be last option.
- Is there anyway I can disconnect all the strict typedef files from the member library files? i.e single click to remove all typedefs in all member files of an LLB or lvlib?
Please find the attached llb file and you could see that all member files have dependency with a lvlib file which is part of the attached llb. I just want to remove the lvlib dependency. Sorry if I am over communicating.
Thanks in advance,
Neo
-
Hi all,
I was not successful in running the SMTP example provided for PDA Mobile by NI,though I used the same POP and SMTP settings to send mail through my native e-mail client(mobile).
I got following error message from E-Mail server:
"553 Sorry, that domain isn't in my list of allowed rcpthosts."
Listing the arbitration between PDA SMTP VI and e-mail server.
Message to server :
- HELO 10.20.5.32
- MAIL FROM:<info@goflexteq.com>
- RCPT TO:<info@goflexteq.com>
- DATA
- To: info@goflexteq.com
From: info@goflexteq.com
Subject: Project details Test. - QUIT
Response from Server:
- 220 smtpauth02.prod.mesa1.secureserver.net ESMTP.
- 250 smtpauth02.prod.mesa1.secureserver.net.
- 250 Sender accepted.
- 553 Sorry, that domain isn't in my list of allowed rcpthosts.
I would really appreciate if any of you could interpret this arbitration and let me know what the issue is.
Thanks in advance,
Manu Mohan
- HELO 10.20.5.32
-
QUOTE (David Boyd @ Mar 3 2005, 11:02 AM)
I haven't tried this, but the Tab Control reference has a property called Pages[], and methods called Add Page, Dup Page, and Remove Page.A Page reference has properties for getting all Controls[], Decorations[], AllObjs[], as well read/write properties for its visibility, enabled state, caption, page description, etc.
My first guess is that the 'New VI Object' primitive could create a control and you could specify a Page as its owner's reference.
It's too late for me to try this right now. If you have trouble getting this to work, post back and I'll see what I can do.
Best regards,
Dave
Page addition option was not available in Methods of the Pages[].
Disconnecting from *.lvlib
in Application Builder, Installers and code distribution
Posted
Got it right this time. Though I was using LV2010, my scripting was disabled. Thanks a lot for such a detailed and clear explanation. You are absolutely right, I should spend more time to explore these properties. Attaching what I have
done,If it's going to be useful for another wire-worker.
@Jon, I don't see a way to give kudos here. Thanks a lot.
I don't use LAVA very often, I think I should visit here more often .
Oops, missed the attachment here.
disconnect from library.vi