Michael Aivaliotis

QUOTE (gmart @ Mar 19 2008, 06:15 AM) Aaaarg! Definition of "relative"? Response from support: QUOTE Thank you for contacting National Instruments. The relative path seems to work correctly when the default is used for the Destination Directory. I have tested out several scenarios and it seems that the relative path is used as long as the Destination Directory points to the location of the LabVIEW Project or a sub-directory within that folder. I have also found that it works when it points to a folder that is next to the folder containing the project. I'm going research this issue further and get back to you with more information. In the mean time, could you test out the following destination directories? 1) D:\_Projects\Experiments\subfolder\buildpathissues\ 2) D:\_Projects\Experiments\subfolder\buildpathissues\source 3) D:\_Projects\Experiments\subfolder\buildpathissues\source\mycode Please let me know if you see relative paths when copying these Source Distributions to another location on your hard drive. Thanks! Just to remind y'all, the project file is located under the "mycode" folder. So out of the three above folders, only the last 2 remapped correctly when the project file moved. I consider this a bug. What do others think? It sounds like, "leave everything as default and it will work". huh? The one good thing from this discussion is that now I finally understand the mystery of why the destination path behaves like it does and I hope I've saved others form smashing their computers to the wall.

Great tip, I just added it to the Wiki. http://wiki.lavag.org/Tips_and_tricks#Palettes

QUOTE (Aristos Queue @ Mar 19 2008, 02:35 PM) A representation of the VI is staring right at you in the palettes and you are helpless but to stare right back at it. Such a powerful tool as the palettes and so underutilized. One option (which really only works if the template is not calling other template VI's) is to right click on the icon and select Open VI. Then you can save it as a normal VI. As I mentioned, not practical if the template calls other template VI's.

Thanks for the feedback Yen. Even though the color scheme is what it is, I just want to point out that the NI Forums have pretty much the same scheme and a white background. Of course this doesn't mean anything I just want to mention it as a comparison because you hang out there as well. I assume you don't like the NI Forums colors too? I'm just asking out of curiosity.

QUOTE (Eugen Graf @ Mar 17 2008, 09:48 AM) So it appears you started the discussion to introduce a multi-language tutorial site\blog and now it appears it's just going to be English forums. That's fine, just don't try to deceive people. We're all working here to simplify things and unite the LabVIEW community as much as possible. It's hard enough trying to survive under the NI juggernaut (who now is creating their own Wiki, hey why not get our customers to build our site, heck they're solving their own problems on our forums anyway, and... let's not contribute to an existing Wiki like let's say oh i don't know, LAVA, because it's not "made here"). I don't think it's productive to create yet another LabVIEW forum. That's one of the reasons ExpressionFlow and LAVA have teamed up. We felt it was for the good of the LabVIEW community as a whole. Of course, as always... It's a free world. Well, most of it anyway.

QUOTE (Aristos Queue @ Mar 19 2008, 12:03 PM) Stephen, that's not funny.

I know about this. I'm already looking into it. Sorry I didn't reply sooner.

Please check again. It should be fixed now.

In 7.1 there is a feature called compare VI Hierarchies and works well. The key is to create a toplevel VI that contains all of the subVI's. You may already have one if you have a User interface that calls code. Otherwise create a blank VI and drop the subvi's onto the diagram and save it. Do this for both versions of code. Now open the tool under Tools>Compare>Compare VI Hierarchies. Where it asks you for the First Hierarchy and the Second Hieratchy you need to select the two toplevel VI's you just created. Notice that it states the second Hierarchy will be renamed. This is temporary. What this implies is that you probably want to make your edits on the First hierarchy since it stays intact (not renamed).

Well all of this has prompted the install of some more new awesome word and puzzle games (and even one math one) that I think are more geared towards the LAVA engineer-type crowd.

I'm honestly really so sorry everyone. The score removal was not intentional. Blame it on bad backend software that doesn't warn you when a irreversible operation will happen. It was my first time using that arcade admin control panel. I promise that this won't happen again and I'll try to bring back some of the original games.

I'd also like to welcome ExpressionFlow to the LAVA community and I am looking forward to the discussions that will follow. The ExpressionFlow Blog has proven itself as a source of advanced LabVIEW topics and coding techniques. It was only fitting that LAVA offer to host forums in support of ExpressionFlow Blog and software support discussions. A lot of care was taken to balance the look and feel of both sites and we hope we have accomplished our goal. Let us know if there are any technical issues we haven't caught. So let's extend a warm LAVA welcome to Tomi and the ExpressionFlow team. :beer:

If it was me, I would just spend the money on an iPhone.

I've reported this to NI support.

Ok, thanks I will look into it.

There are four options here. Pick which one applies to your situation and use it. If you want to rearrange the position of buttons or rename them then we can discuss that but basically everything you could want is already there for you. Also, compared to NI Forums, LAVA has essentially the same functionality plus a few more. I don't have time right now to give a detailed description of each option. I'll do that later tonight.

Nice site, besides the fact that it's devoid of any useful information.

Just click the reply or fast reply. It doesn't include the previous post. The button you refer to is the reply with quote. That's why it has the quote symbol.

Well, In repairing the damage from the cheater, we lost a lot of the high scores in the arcade. Sorry. I also took the opportunity to install some new games and remove most of the old ones that had the cheating bug.

Thanks. It's been taken care of.

Yes! I won the bet. PS. This is bad and is definitely a crappy limitation.

QUOTE (gmart @ Mar 17 2008, 09:58 AM) No problem.I have the following setup: Original Configuration: D:\_Projects\Experiments\subfolder\buildpathissues\source\mycode\Untitled Project 1.lvproj The build spec defines a destination as: D:\_Projects\Experiments\subfolder\buildpathissues\builds Now I move the subfolder here: D:\_Data\subfolder\buildpathissues\source\mycode\Untitled Project 1.lvproj Now when I open it in the new destination i see this in the build spec destination: D:\_Projects\Experiments\subfolder\buildpathissues\builds Nothing changed. The relative build destination is still the same, so why didn't the build spec reflect the new location?

[LV 8.5] I've just only now noticed this issue. When I open the exe build specification on different computers, where the *.lvproj file is located in a different folder, the Destination directory path setting in the Information section is absolute. This has serious implications in a multideveloper environment. Each developer has their project folder in their own location and when they open the build it will fail to execute because the path doesn't exist on their machine. This destination path needs to be relative to the project file. How many years has NI had to get this right?

Maybe people should update their LAVA profile with the LabVIEW version used. Then I can query the database for a complete list. :ninja:

Ya, I don't notice the resize. I'm running 1920x1200 (isn't everyone?) and I didn't even no it was taking your native resolution into consideration. I'll look into it some more. Update: Ok, Yen I think I finally figured this one out. The images should be fine now even on low resolution systems. Check it now.