Jim Kring

QUOTE(Tomi Maila @ Mar 1 2007, 07:54 AM) EXE's require at least one window to be open, otherwise they are terminated.

Did somebody say, "low overhead"? http://forums.lavag.org/index.php?act=attach&type=post&id=5064 Malkovich malkovich? Malkovich, -Malkovich

QUOTE(Amaury @ Feb 27 2007, 10:40 PM) Amaury, SVN does not keep track of whick revisions have already been merged into a branch. I believe that it is something that the SVN developers are working on. There is a tool that is commonly used to achieve this called http://www.orcaware.com/svn/wiki/Svnmerge.py' target="_blank">svnmerge. It is written in python and you can run the script directly or run a compiled exe in windows. Thats about the only solution, I think. Thanks, -Jim

On my commute to work, this morning, I was doing what I often do... listening to the latest software engineering radio podcast. This time it was Episode 47: Interview Grady Booch (Booch of the Gang of Four, Design Patters book). First, I was tremendously impressed and excited by the fact that se-radio was interviewing Booch -- he's a real heavy hitter in the software engineering world. And then, I was blown away that Booch mentioned... LabVIEW as a domain specific programming language for instrumentation and electronics (despite the fact that I was just a bit little disappointed that he perceived LabVIEW as a DSL and not a "real" programming language)! Anyhow, it's really cool that LabVIEW (and graphical programming, in general) is starting to become more visible in the software engineering circles -- it's only a matter of time until we all program this way

QUOTE(Michael_Aivaliotis @ Feb 26 2007, 01:10 PM) Right now, OpenG libraries do not support the NI Example Finder's keyword search feature. I could add support, but this would be require some more work (specifically, using the http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/prep_vi_for_ni_example_finder/' target="_blank">Prepare Example VIs for NI Example Finder tool). This is basically the reason that I started the discussion topic/poll.

QUOTE(BrokenArrow @ Feb 26 2007, 08:11 AM) Richard: I agree with Mike. I think you'll be OK. Talk to your local sales reps and see what they say. They are the ones who will be losing a potential sale, but 99.9% of the time they will want you to be a happy and faithful customer It's just good business sense.

QUOTE(chrisdavis @ Feb 26 2007, 08:09 AM) I like the BSD. Here are my thoughts on why OpenG is now using BSD.

QUOTE(David_A_Moore @ Feb 26 2007, 04:26 AM) Oops. That was my intention. I have just fixed that.

I'm curious about peoples' usage of the NI Example Finder. Please vote in the poll and post any thoughts here. [uPDATE] If anyone is curious about why I'm asking these questions, here's your answer.

QUOTE(Aitor Solar @ Feb 21 2007, 04:15 AM) Aitor: Under which license are you distributing the XNode Manager tool? I would like to volunteer to help package this up so that people can install it using http://jkisoft.com/vipm' target="_blank">VIPM.

QUOTE(Tomi Maila @ Feb 24 2007, 03:09 PM) In my opinion we desperately need native, by reference, active objects with support for events and arbitrary and dynamic secure distribution across multiple execution targets. Think we'll see this anytime soon? If NI thinks that we (I) don't need these things, then they don't understand our (my) needs. The current LVOOP is great, though -- its a right step in the right direction at the right time. It just doesn't solve my day to day OOP needs.

QUOTE(tcplomp @ Feb 24 2007, 02:43 PM) Thanks. Index Array Elements is one of my favorites of the new additions. Check out how the icon and conpane changes when you change from a 1D array to a 2D array input. <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=5,0,0,0" width="640" height="496"><param name="movie" value="Index_Array_Elements.swf"><param name="quality" value="high"><param name="bgcolor" value="#ffffff"><embed src="http://forums.lavag.org/index.php?act=attach&type=post&id=5023" quality="high" bgcolor="#ffffff" width="640" height="496" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"></object>

Hello LAVA'ers, There is a new version of the OpenG "Array" library (oglib_array package) available. This library contains several routines manipulating arrays. This release... See here for more info.You can download+install this package using VI Package Manager. Just press the "Check the Network for Available Packages" button to refresh your package list. Thank you,

QUOTE(Michael_Aivaliotis @ Feb 24 2007, 12:20 PM) Hmmm, my guess is that customfile.lava is not a valid LabVIEW file (that's what the error message says). If you have a non-LabVIEW file that you want your exe stub to handle, you need to pass it as a user-defined command-line argument, according to LabVIEW conventions (pass it after the double hyphen "--"). QUOTE("LabVIEW Help") Application:Command Line Arguments Property Returns an array of user-defined command-line arguments passed when LabVIEW launched. User-defined arguments start after two hyphens (--) surrounded by spaces in the command line. The first string in the array is the name of the executable launched. This property does not return the name of the VI launched or the LLB that contains the VI. If a user-defined command-line argument contains double quotation marks ("), this property returns the argument without the quotation marks. If you use this property in a stand-alone application, you can pass all arguments as user-defined arguments so you do not need to enter the two hyphens before user-defined arguments in the command line. This property is similar to the Pass all command line arguments to application option on the Advanced page of the Application Properties dialog box. Example

QUOTE(tcplomp @ Feb 24 2007, 06:07 AM) Now you're giving away all my secrets Yes, that's pretty much how everything works. One key aspect is that the .mnu files for libraries are linked to the VIs in the installed location. And, the installed location is permanent -- we never ever change the installed locations of library VIs. Since the installed location is under user.lib, the .mnu files link to the library VIs using paths relative to user.lib (a feature/quirk of LabVIEW is that files beneath user.lib, vi.lib, instr.lib use paths relative to those folders). So, one benefit of this feature is that the .mnu files can be moved to arbitrary locations and they will always find the library VIs, since the libraries are in a permanent location relative to user.lib. The downside of this feature, is that you cannot move the library VIs to new locations or they will have trouble finding other library VIs. But, it is easy for us to always install them in one and only one location, using VIPM.

QUOTE(Michael_Aivaliotis @ Feb 24 2007, 03:26 AM) Post a copy of your windows registry so that it's easier to help you debug But seriously, some examples of your key/values would help. I'll bet you're just missing some quotes around your paths.

QUOTE(JFM @ Feb 23 2007, 12:07 PM) This is not a bug, it's a feature. Here's what's up... There are two types of "time" absolute time and relative time. The timestamp is an absolute time datatype and a floating point is (or should only be used for) relative time. Subtracting two absolute times results in a relative time: 2/23/2007 - 2/21/2007 = 4147200.000 seconds (2 days). Subtracting two relative times results in a relative time: 3.0 seconds - 0.8 seconds = 2.2 seconds Adding two relative times is nonsensical: tomorrow + today = huh? (unless you're living in one of alpha's parallel universes) Adding a relative time to an absolute time results in an absolute time: 2/23/2007 21:00:00 + 5.0 seconds = 2/23/2007 21:00:05

QUOTE(chrisdavis @ Feb 22 2007, 07:42 PM) Hi Chris, For VIPM's documentation, JKI uses ComponentOne's Doc-To-Help, which can compile MS Word documents to various forms of help documentation -- we use the HTML output format. This allows us to have cross-platform and web-based help documentation. The documentation process starts by first developing a specification. This is an internal document that describes what the software needs to do, from the perspective of validating the final product's features. Then, once the features are implemented, portions of the spec are used in the final user guide, which is written from the perspective of helping users understand the products features. Thanks,

QUOTE(linnx @ Feb 22 2007, 08:11 AM) linnx: Thank you for expressing your concerns and for working with us to help make the LAVA forums as good as they can be

QUOTE(dsaunders @ Feb 22 2007, 08:26 AM) David, We will continue to do everything in our power to make VIPM a must-have app Rest assured, we are very committed to the Community Edition of our product, as we are very committed to the LabVIEW community, in general. If you're impressed by what the JKI team can do with VIPM in our spare time (we are a consulting company, by the way), can you imagine what we might do, if VIPM were our day job? I can sincerely say that your support of the professional version of VIPM will help support the LabVIEW community in various indirect ways. Want proof? Since the release of VIPM 1.0 in January 2007 (just over two months ago), the rate of OpenG library usage has increased by (20x). Thanks for your support, -Jim

QUOTE(linnx @ Feb 21 2007, 02:33 PM) linnx/romulus, This is a cross posting, as are nearly all of your postings to LAVA. PLEASE, if you are going to cross post, then put a link to your other post. You are basically asking people to waste their time (asking for unnecessary duplication of effort) and depriving people from useful information (possible answers on the other thread). :!: For example: LAVA :: NI LAVA :: NI LAVA :: NI

QUOTE(TiT @ Feb 21 2007, 01:39 PM) You should be able to copy your "My Computer\LabVIEW Data\8.2\Palettes" folder from one computer to another and it will copy all of your palette edits to the new computer. Again, don't mess with anything under the LabVIEW installation folder. JKI is in the concept phase for tools to manage your LabVIEW preferences and palette edits accross multiple LabVIEW versions, using VIPM. I'm as excited as you are and can't wait

QUOTE(Aitor Solar @ Feb 21 2007, 12:12 PM) Thanks -- I'll see if I can relink them. Also, this will be a problem for other users too, so it might be best to relink everything correctly and then repost

QUOTE(Neville D @ Feb 21 2007, 11:25 AM) No, that won't work. LabVIEW (8.x) keeps your palette edits inside the "My Documents\LabVIEW Data" folder. It's not advisable to copy anything from beneath one LabVIEW folder to another -- it's begging for problems (much like manually editing your Windows registry )

Looks nice. However, it won't run, because it is missing a couple VIs: "borrar error.vi" and "convierte vilib path (from string).vi" Thanks,