gmart

Actually it's A-ish. Files that are under the LabVIEW directory are "bucketed" in a LabVIEW folder. So from the example: A: application.exe/main.vi application.exe/subfolder/subvi1.vi application.exe/LabVIEW 2009/vi.lib/vilibVI1.vi application.exe/LabVIEW 2009/user.lib/_OpenG/openGVI.vi application.exe/LabVIEW 2009/instr.lib/Instrument Driver1/initialize.vi Adam is correct regarding writing your own wrappers. I believe that is mentioned in the help as well.

You can consider the 64 vs 32 bit application similar to building an app on Windows that will run on Mac. Essentially we would need to have the ability to cross compile VIs for a different OS (in this case bitness being the difference). I am not aware if there are plans to support building for the different OS's.

No. 64-bit LabVIEW will only build 64-bit apps. 32-bit LabVIEW will only build 32-bit apps.

I believe you need to install an integration plugin. See this Microsoft KB - http://www.microsoft.com/downloads/details.aspx?familyid=87E1FFBD-A484-4C3A-8776-D560AB1E6198&displaylang=en

QUOTE (silmaril @ Jun 11 2009, 11:32 AM) If Perforce SCM works for you then stick with it. The Perforce command line provider works across all platforms, but if you're on Windows only, SCM will work for you.

QUOTE (jed @ Jun 8 2009, 02:53 PM) As of LabVIEW 8.0, the Perforce Command Line provider has been available. None of the VIs (except for a couple) are password protected.

QUOTE (shoneill @ Jun 8 2009, 07:51 AM) Perforce SCM is a Perforce written provider. The dialogs and functionality provided there are provided by Perforce. The Perforce Command Line provider is a set of LabVIEW VIs that provide SCC functionality (including UIs) by using Perforce's command line tool (p4). For the most part both providers provide a similar level of functionality. An advantage of the Perforce Command Line provider is that it is cross-platform. Also, by using the command line, operations such as a native LabVIEW diff can be performed. You can diff LabVIEW files with Perforce SCM, but you have to configure a tool (such as lvdiff) from the client to do this.

QUOTE (jed @ Jun 5 2009, 03:34 PM) For the record, the P4 SCC plugin (Perforce SCM) is not written by NI (The "Perforce Command Line" provider is). LabVIEW calls into Peforce's implementation of their SCC provider. The functionality exposed through the Tools>>Source Control menus is based on a common source controlled interface so it will lack customization for each provider.

QUOTE (Ton @ May 7 2009, 03:46 AM) That is the reason that was given to me.

I had had the same reaction when I first ran into this. I asked a fellow developer and he said that from a computer science perspective, this results is correct. I don't recall the details but this is not considered a bug.

The trailer tease about Uhura and Kirk sure made their kiss back in the original series look like Sunday school.

Perforce has a plugin for Windows Explorer as well. It installs automatically. I now do not install it since one of the early releases had a problem hanging my computer when the server was down. Anything that integrates to Explorer that can connect to a remote server is asking for trouble in my book. Of course that's how Tortoise works (and has worked fine for many releases) but I'm still leery of Explorer plugins.

QUOTE (Darren @ Apr 21 2009, 11:26 AM) I was engineering student. That feature never worked for me . QUOTE (crelf @ Apr 21 2009, 01:27 PM) And that, ladies and gentlemen, is the difference between a geek and a dork. I'm with you gmart - I had a Casio when I was at uni, but my major was Physics and we were expected to do all the math in our heads I've still got it, and use it in the office all the time: Oh yeah! ...although I'm not sure what an unnatural display would look like. I think I have calculator envy :thumbup: . Down with reverse Polish notation!

QUOTE (Darren @ Apr 21 2009, 10:17 AM) I am proud to admit that I bucked the geek train and refused to use an HP calculator in college. I had a Casio FX-6300G (http://www.rskey.org/detail.asp?manufacturer=Casio&model=fx-6300G).

QUOTE (jpdrolet @ Apr 8 2009, 08:54 AM) Perhaps. The requirements are interesting. I am not well versed on Perforce's needs so you'd have to ask them why they chose to do this. Just so I'm clear, you are not able to use the P4SCC 2008.1 because it wants a newer server correct? I believe the original problem you reported was fixed in a P4SCC with a 2005.x version and higher (though I'm not sure). You would need to verify this with Perforce, but I think it's possible to have a different version of P4SCC, P4, P4Win and the like all on the same machine.

QUOTE (jpdrolet @ Apr 8 2009, 07:47 AM) You shouldn't need to update the server version. What is needed is the later version of the P4SCC plugin. This plugin is typically installed with the P4Win or P4V installations. As far as the revision graph feature, Perforce SCM is Perforce's implementation of IDE SCC integration. So they expose whatever features they choose. I checked my P4Win (which is 2008.2) and it does have the Revision Graph option. I'm not sure if support for this is tied to the version of the server you are running.

QUOTE (jpdrolet @ Apr 7 2009, 09:21 AM) This is a combination of two bugs - one LabVIEW and one Perforce. The Perforce 2004.2 was showing this dialog whenever there was an fstat problem. This was corrected in a later version (the current version is 2008.2). Secondly, LabVIEW is checking source control status on files during a build. This is a known issue and has been reported to LabVIEW R&D. Updating the Perforce version should eliminate the dialog.

QUOTE (335x @ Apr 5 2009, 10:47 PM) Thanks for the response.

QUOTE (335x @ Apr 4 2009, 10:37 PM) Out of curiosity, did you try to search LabVIEW's menus or help and could not find your answer or are you asking before having done this?

QUOTE (jlokanis @ Mar 26 2009, 04:52 PM) App.kind returns what type of application is running the VI. So in the development environment, the property will return "Dev system" (or whatever it is). If a VI is loaded via the run-time engine, the property should return "Run Time System".

QUOTE (jlokanis @ Mar 26 2009, 02:07 PM) You could try using the App.Kind VI server property.

QUOTE (Jim Kring @ Mar 18 2009, 06:44 PM) In general, no. I was trying to cover my bases since it's possible that a library owns a class and such. In that case, loading a library would load VIs but only due to a class being a member of the library.

QUOTE (Cmal @ Mar 18 2009, 03:36 PM) A clarification. A project ,by itself, does not load VIs into memory when it is loaded. It is able to determine what dependencies are needed/used without loading VIs into memory. The project does load project items such as libraries or classes which may load VIs.

Are you able to whittle this down to where driver's are not involved? Also is the application able to be posted for evaluation?

QUOTE (Dan DeFriese @ Feb 12 2009, 04:30 PM) As of LabVIEW 8.5, you can configure source control project settings at a LabVIEW project level. You still need to enable source control for the environment though.