Yair

QUOTE (pdc @ Oct 30 2008, 04:37 PM) Someone has been systematically assassinating all the high level people so that the low level people can rule the world. I guess that alfa needs to be very worried now.

That's great. <cynicism> How much polution is generated by transporting the hardware? </cynicism>

LabVIEW 7.1 did not have the project environment and therefore does not have this property. If you want to scan a folder for VIs which aren't used, you can try searching LAVA for old posts by E. Blasberg. One of them should have a tool for finding unused VIs.

Stephen, how about "dependency callers"? I think it pretty accurately describes these, even if it's not immediately understood. Philip, while terminus is a great word (and you just brought back some nice Asimov memories), I don't think it accurately describes these, as they are NOT end points. More often than not they are probably in the middle of the call chain and the only thing making them special is that they are at "the end" of the project. P.S. Stephen, what's the use case for finding these?

Oh, yes, you should definitely not let poets lie to you. Also, don't take legal advice from people on the internet and be sure to brush your teeth well. And remember to wear a sweater.

Cross posted to the NI forums. It's considered polite to link to cross posted threads to avoid having people do duplicate work.

VIPM is a separate application, so it will work with any LabVIEW version (at least any version that comes with a VI server connection, which 7.1 does). I think you need to download and install the relevant RTE separately, but I'm sure the JKI site has the exact instructions. As for the OpenG packages, most of them were written using LV 6.1, so they will work with any version newer than that, but some were written in newer versions and you won't be able to use them. VIPM manages that for you as well.

QUOTE (normandinf @ Oct 17 2008, 11:16 PM) Well, I did have a diet recently*, so... * No, I didn't actually have a diet.

Other than the normal advice you would get from some vocal members of not using express VIs, here are two things you can try - Call the subVI called by the express VI directly. You won't get the config dialog and you will have to set up an easy way to do this, as the VI will not be in the palettes by default. Create a blank VI and place the express VI in it. Then change the display and add the calling VI to your palettes as a merge VI. I'm guessing this will work, but I haven't tried it.

I'm not sure if it's against the license (at least if you're using an older version of LabVIEW to write the scripting code), but I haven't looked at the EULA and I'm not a lawyer. By the way, if you can make a case for needing scripting and you ask nicely, NI might actually give you a scripting license. I've heard of people who got that, but I have no idea of the details and I assume it's a small amount of users. FWIW, there are also other ways to do dynamic GUIs (e.g. picture control, making "enough" controls, etc.), but they each have their own set of problems.

QUOTE (Gabi1 @ Oct 12 2008, 07:17 PM) You don't have to do without, as long as you don't mind implementing the code for each OS where you want this. As mentioned, there is already some code online for Windows. Once you do this, you will probably see why NI does not take the time to do it. Incidentally, while I thought about this a long time ago, I never actually needed it for any application.

I see that we can't access it from the thread options button any more, but when I clicked a link from Google, it came out in threaded view and it also made all the other threads appear as threaded. Is there any way to get rid of it completely?

QUOTE (LV_FPGA_SE @ Oct 10 2008, 05:08 AM) I did that once as one of our demos when I wanted to draw people to our stand in a show. I wrote a simple tic-tac-toe implementation, so that when one player made a move, the move appeared on the other player's board. I then tweaked it and deployed it to a laptop, to a 15" touch screen PC and to one or two PDAs communicating over Wi-Fi, so that people could play each other with any combination of devices. The concept was to have something very simple that you could finish in about 20 seconds, but which would catch people's attention.

QUOTE (Aristos Queue @ Oct 11 2008, 02:14 AM) Stephen, that will only work for the names (and I'm not actually sure the OP only wants to hold VI references). As mentioned, most references in LabVIEW (not including queues or notifiers obtained by name. Good for you) are GC'd when the top level VI in the hierarchy which originally created them goes idle, even if the subVI holding the reference is held in memory. I would say that the solution to this would be to create a daemon (implemented as a dynamically called VI) which will be responsible for acquiring and handing out the references, but since there aren't enough details about the actual requirements of the app, it's hard to say. In any case, it's also important to note Jason's note about app instances. If these really are separate instances, the references will not help, as they will not work across the instance boundary.

Many people have interacted with microcontrollers and if you search both here and in NI's forums you should find many threads. Additionally you can find shipping examples in LabVIEW's example finder (in the help menu). You probably want TCP related examples. You should start by going through some tutorials first, though.

I agree with Stephen, but there's a simple middle path - NI can simply put an intern on it and ship more custom probes with LabVIEW (like Darren's history probes, which can be very useful). The UI for selecting probes is simple enough once you know it's there.

QUOTE (HChandler @ Oct 3 2008, 08:37 PM) Maybe you should have used a better tool . QUOTE (Aristos Queue @ Oct 3 2008, 11:49 PM) Use the Type Cast node to cast your refnum to an int32. Then use the Type Cast node again to cast that int32 to any refnum type you desire. Welcome to the dark side, Stephen. All these years around those supersecretprivate hackers must have poisoned your mind. P.S. Any reason for taking a detour through the int instead of casting directly to the desired class?

Using scripting, you can also add a VI to the Tools menu which will get the Selection List[] property for the current VI, check each element to see if it's a comment, and if it is, add its text to the VI's description. The Comment class does not have an exposed Text property, so you can type cast it to the String class. Of course, you can also do this as a floating tool which will be open all the time. If you want to save time on some of code, you can lift code from the CCT or the tunnel wiring wizard.

Stephen already gave you the basic answer - the dynamic dispatch mechanism works by name, so all you need to is create this method only in the parent and in the specific class you want. In the parent it will do nothing and all other classes will call that implementation. In the child it will do whatever you want (e.g. build an array). I'm guessing the reason Stephen suggested building an array of parents is that having the link to the child in the parent breaks encapsulation, since the parent should not know about the child. Once you have the array of parents, you can simply cast all of it to an array of children.

QUOTE (jdunham @ Sep 26 2008, 10:03 PM) Anything wrong with http://forums.lavag.org/-t8976.html&view=findpost&p=41774' target="_blank">this? Works before 8.6 and IMO better in some ways than QD. The only real issue is getting the names, but hopefully I should have a solution for that using the same method NI uses in 8.6.

How about these books? While not strictly LabVIEW books, they are certainly good books for life and could probably help people starting with LAVA.

It's found in <vi.lib>\utility\lvclass, but I think it was only added in 8.5. I guess that before that you can implement a dynamic dispatch method to return the path, but you would need to implement it for each class.

You can use the Get LV Class Path VI from the class palette. I'm not sure if it's there in all versions.

If you click your name in any post, you should have a View Member's Posts option. Additionally, in the profile page, there is a similar ring at the left side, under the member's name.

What happens if you create a UDL file and try setting it as the provider? Also, did you try searching Google or the MSDN?