gmart

QUOTE (Antoine Châlons @ Jan 30 2009, 07:47 AM) To clarify, in order to build applications (i.e. EXEs), you need the LabVIEW Professional Development System or LabVEW Base/Full with Application Builder. For LabVIEW Base/Full, Application Builder is an additional component that is purchased separately - http://sine.ni.com/nips/cds/view/p/lang/en/nid/10731

QUOTE (Yair @ Jan 29 2009, 11:42 AM) I see your point, but I think a better analogy is that when you log into your Amazon account and select the web site to remember you, a cookie is placed that lets you log back in again without having to enter your information (including passwords). Obviously, a password entered in another app should not apply to LabVIEW. Within LabVIEW, I am guessing (I do not know for a fact) that the caching is for ease of use. While "better" security might be to ask for passwords at all time, it makes operations such as mass compile or common development actions could become unwieldly. Could two VIs from different developers have the same password? Yes. I think that scenario would be rare though (so don't make your passwords "12345" ).

QUOTE (neBulus @ Jan 29 2009, 09:24 AM) Once a password is entered, it stays cached until you restart LabVIEW or clear the cache.

Check for any network printers that can no longer be accessed. LabVIEW looks up printer settings when the VI Properties dialog comes up. If a network printer is no longer accessible, then the dialog times could take while before it times out.

QUOTE (bluesky @ Oct 17 2008, 11:56 AM) Thank you for the information. There appears to be a slight slowdown in general, but not an across the board 2x difference. Some applications have been reported to be slower by this factor, but it is on a case by case basis. Thank you for reporting this.

QUOTE (bluesky @ Oct 16 2008, 06:40 PM) Do you have the service request number? I am not aware of build times slowing down by 2x between versions. In your particular situation, do you have build times for both 8.5 and 8.6?

QUOTE (km4hr @ Oct 16 2008, 11:19 AM) You can create a new LabVIEW project (File>>New Project...) which will have a Build Specification node. When you right-click on it, you will see a list of build types you can create. If the application builder is present/licensed, you will see an option - Application. You can get more help regarding build specifications by selecting Help in the right-click menu.

QUOTE (Vladimir Drzik @ Oct 15 2008, 07:49 AM) Typically, you can configure this within the SCC provider's client. If you are using the Perforce Command Line provider, in the Tools>>Options Source Control page, the option to not lock files is located as an advanced option.

QUOTE (Phillip Brooks @ Sep 11 2008, 11:15 AM) And VI Profiler

QUOTE (Chris Davis @ Aug 29 2008, 02:57 PM) In 8.6, the built in icon editor does not support icons larger than 48x48. Fortunately, there are now many third party icon editor programs that do a good creating and editing "Vista" style icons.

QUOTE (Darren @ Aug 29 2008, 09:50 AM) Plus the fact that we have your INI token that you care about, places it in the ">0" bucket :thumbup:

QUOTE (Yair @ Aug 28 2008, 01:53 PM) Regardless of the intelligence level of the CAR , crashes are never a good thing. Now just because it's CAR'd doesn't mean it might not end up being filed under the "who in the their right mind would make a 10000 frame stacked sequence structure AND THEN replace it with a flat sequence" bucket. That, truly is an honor reserved for a very few.

QUOTE (Phillip Brooks @ Aug 28 2008, 01:15 PM) This issue has been reported to R&D (CAR 124168).

Analysis support is a component of the Run-Time Engine. The installer has an option to include (the default) analysis support. You could verify in the Advanced Installer settings that the "Analyze VIs Support" is checked. You could also try reinstalling just the 7.1 RTE (which I believe you can download from ni.com).

QUOTE (Darren @ Aug 21 2008, 04:36 PM) This discussion reminds me of a NI Days presentation I did where almost every customer told me that they don't use local variables because NI "told them" not to. Instead many were using control references wired to a property node to read/write the value property. I explained that that method was much much slower in execution. Many were shocked. I stated that locals do have their place in LabVIEW code. So the same can be said about sequence structures - flat or stacked. They are not intrinsically evil (they're just drawn that way). They are a tool that should be used properly. So I agree with Darren and Aristos on the Three Button dialog. Yes, it could be implemented another way, but the current implementation is not an abomination. What was an abomination (please forgive me Aristos ) was what that VI looked like *before* a flat sequence was used .

QUOTE (crelf @ Aug 18 2008, 08:10 AM) Careful, some may accuse half the LAVA group of working on the Subversion code base

QUOTE (Ton @ Aug 15 2008, 11:39 PM) I found a download page for the AccuBridge for Microsoft SCC integration here - http://www.accurev.com/download_ab_2008_2.htm#note3 Assuming that is their support for the Microsoft SCC interface (pretty good chance), in theory, it should allow usage of Accurev from within LabVIEW.

QUOTE (Val Brown @ Aug 16 2008, 03:31 PM) There is no built in mechanism to copy build specifications between projects. Since the build specification information is saved in the project file, you could perform a Save As on the project file which will copy the build spec information. One challenge with copying build spec info to another project is that files in the target project may be different than the source project. What would be the best way to handle that? Would the expectation be that the build spec should work or that the user would need to "fix it up"? In general, it is not desirable to create new items that are immediately "broken" so that has been a hurdle to having this feature available.

QUOTE (jdunham @ Aug 13 2008, 04:50 PM) You will be asked to save the caller when the caller is in memory. You won't need to save it since LabVIEW will automatically apply the change the next time you load. You will want your final released version saved since automatic recompiling will cause performance to be impacted. This behavior is not specific to using SCC.

QUOTE (jdunham @ Aug 13 2008, 02:49 PM) There is an option in Tools>>Options>>Source Control where LabVIEW will include a list of callers of a VI that are in memory when checking out a file. So in your example, when you check out your typedef, if the callers of the typedef are in memory, those will be added to the list of items to check out. Something to be aware of. By default, the source control dialog box is not displayed during a check out operation. So when callers are in memory, you may get a warning dialog stating that other files will be checked out. If you do show the dialog box, the callers will be listed in the dialog box. The same behavior happens for subVIs (for the use case where you change the connector pane configuration for example).

QUOTE (crelf @ Aug 12 2008, 09:22 AM) What would be nice is if some enterprising individual were to write an SVN plugin for LabVIEW. Then all would be right with the world

QUOTE (Tom Bress @ Aug 12 2008, 07:34 AM) The text in the knowledge base states This integration enables LabVIEW users to access the source control providers from within the LabVIEW development environment. That statement does not imply that you can't use external tools to perform source control (as is done with Tortoise). Also, using the integration in LabVIEW gives you functionality such as prompting to check out on edit that you wouldn't get by using an external tool. The selection of an SCC provider depends on your needs balanced with cost. SVN is a good package and is very popular in this forum. Internally, NI uses Perforce. Perforce has a license model that is essentially free for a 2-user version.

One thing to keep in mind regarding the change to the Report Generation Toolkit. When you build an application that uses VIs that are part of the toolkit, you will run into the name collision issue where some files will be placed outside of the executable.

Someone needs to start a pool to see how long it will take for some bored TSA employee to post the images to YouTube or somewhere else. Anyone who has stock in the maker of the scanning machine should be ready for that day.

QUOTE (Norm Kirchner @ Jun 17 2008, 08:07 AM) http://developer.mozilla.org/devnews/index...0-utc-10am-pdt/ High noon Central time.