Jim Kring

QUOTE(Eugen Graf @ Oct 8 2007, 12:33 PM) Eugen, I believe that you misunderstood my point. I want to easily identify and find all Project Explorer items that are marked as "missing". Resolving the missing items is another issue altogether. Thanks, -Jim

QUOTE(Christina Rogers @ Oct 8 2007, 09:08 AM) Hi Christina, Mac users have been working without file extensions for quite some time and this is the default setting in Windows, now. And, if this a setting were available from the Project's View menu, then users could easily enable or disable it. http://lavag.org/old_files/monthly_10_2007/post-17-1191864980.png' target="_blank"> Thanks, -Jim

QUOTE(Michael_Aivaliotis @ Oct 7 2007, 03:03 PM) Hmmm... required outputs. I could use that. I would make every single error out terminal required.

That was pretty good. But, I think it coulda used a bit more cow bell.

QUOTE(tcplomp @ Oct 5 2007, 10:26 PM) Hi, Ton. I'm not sure what you mean by that. Please explain.

QUOTE(Michael_Aivaliotis @ Oct 5 2007, 02:37 PM) I'm sure you can get a http://wiki.lavag.org/CAR' Number" title='LabVIEW Wiki article on CAR Number' alt='Wiki article on CAR Number' style="border-bottom: 1px dotted #3366BB; color: #3366BB; cursor:pointer; text-decoration:none;" class="wiki">CAR Number if you try

QUOTE(Michael_Aivaliotis @ Oct 5 2007, 01:57 PM) Bold means required input (control) and right side means output (indicator).

QUOTE(Michael_Aivaliotis @ Oct 5 2007, 01:42 PM) I'm sure I won't slow him down too much, along those lines

I wish there were a way to hide the .lvclass extension (and perhaps the file extensions of all LabVIEW native file types, or maybe even all files) in the Project Explorer. Having them visible tends to reduce the signal to noise ratio of my LabVIEW development experience. :2cents: -Jim

Use the Application::Get VI Version(<path>) method. Download File:post-17-1191614935.vi

QUOTE(Aristos Queue @ Oct 4 2007, 02:31 PM) Thanks! I've moved this topic into the 8.5 buglist forum.

QUOTE(tcplomp @ Oct 4 2007, 11:32 AM) Never heard of 'em :laugh:

QUOTE(gmart @ Oct 4 2007, 08:31 AM) I wouldn't say that File I/O functions never worked with LLBs -- a few of them do. For example, the File Exists? function works with LLBs (although I think there is/was a bug that prevented it from doing when running from a built application). http://lavag.org/old_files/monthly_10_2007/post-17-1191513865.png' target="_blank"> And, I'm sure Mikael's probably right about the change in behavior of his application that used the Copy primitive Also, don't forget that you can store LabVIEW class (.lvclass) and xnode (.xnode) files inside LLBs, too, as well at run time menu (.rtm) files and a few other esoteric LabVIEW file types. Cheers, -Jim

QUOTE(george seifert @ Oct 3 2007, 08:40 AM) QUOTE(Jim Kring @ Oct 3 2007, 01:00 PM) I've started doing the same. Another thing that I've started doing (for large projects) is using the Window Task Manager to kill LabVIEW, when I want to close my project, especially if it is showing unsaved changes. Sometimes it can take minutes before LabVIEW shows the "Save Changes?" dialog.

I would expect that, when I do a select Save As>>Copy>>Open additional copy>>Add copy to MyClass.lvclass that the copy should be put in the same project folder and have the same access scope (public, private, or protected) as the original. However, LabVIEW just puts it in the root of the Library (or LVClass) and sets the scope to public. 99.9% of the time, I want it to be in the same project folder and have the same access scope as the original, which means that I have several manual steps to perform after the Save As operation.

QUOTE(jzoller @ Oct 3 2007, 11:19 AM) Joe, I said that the classes should be stored under a "classes" folder inside subfolders named after the respective class. Isn't this a form of "organization on disk"? It certainly isn't disorganization Cheers, -Jim

QUOTE(rkanders @ Oct 3 2007, 08:32 AM) I've started doing the same.

Hi Gabi, I agree that LabVIEW can improve the ways that it allows you to visualize the relationships between classes. Here are a some thoughts... You can see the class hierarchy from the View>>LabVIEW Class Hierarchy dialog. You can use naming conventions to help distinguish between parent and child classes. For example, Heater.Simulator and Heater.Watlow are children of Heater. You should organize your classes on disk, putting them each in a separate folder. It is better to organize them into a flat structure on disk (put all class folders in a "classes" folder), since you may decide to change the inheritance hierarchy later, and it's difficult to move entire folders around to reflect the new class hierarchy. In LabVIEW 8.5, when you double-click on a dynamic method subVI on the block diagram, it opens the Choose Implementation dialog, which shows you a tree view of all the implementations of the different classes. Take a look at this blog article by Christina Rogers -- there is a video of how to use this great new feature. Cheers, -Jim

QUOTE(AnalogKid2DigitalMan @ Oct 2 2007, 10:31 AM) One of the cool features of NI's website is that most pages have an RSS feed. Here is the RSS Feed for the 8.5 Issues page. Unfortunately, this is not an RSS feed of individual issues -- I assume (but I could be wrong) that the feed will produce a new entry whenever the page content is changed.

QUOTE(Michael_Aivaliotis @ Oct 1 2007, 05:24 PM) I can reproduce the error on my machine.

QUOTE(Aristos Queue @ Oct 1 2007, 01:11 PM) Maybe we should all pool our money together to get you a slower computer

JKI is excited to announce the 2nd beta release of VIPM Professional Edition 1.1. This includes improvements resulting for your feedback -- thank you! Please see the VIPM 1.1 - Beta 2 Release Notes page for more information about the improvements made in this release. To download and install VIPM Professional Edition 1.1 Beta 2, visit http://jkisoft.com/vipm/download/.

QUOTE(NormKirchner @ Sep 26 2007, 11:08 PM) If anyone can...

QUOTE(NormKirchner @ Sep 26 2007, 04:02 PM) That sounds a little bit like, "how much wood would a woodchuck chuck if a woodchuck could chuck wood? :laugh: Your question is not very clear to me and I don't understand the context. What are you trying to accomplish?

QUOTE(JFM @ Sep 26 2007, 09:42 AM) In Windows XP SP2 there is a limit to the number of sockets that the OS will allow you to open, in order to prevent viruses from spreading (talk about a band-aid solution). There is a patch tool, here (use at your own risk), that will allow you to adjust this.