Michael Aivaliotis

QUOTE (neB @ Mar 31 2008, 05:45 AM) Nope.

QUOTE (Yen @ Mar 28 2008, 03:06 AM) I'm not convinced that you have a problem. You say that it used to work and now it doesn't. Why? You say you upgraded to the latest variant tools and it worked. Then after a while it didn't. Could you post the data structure so we can try it out and benchmark it?

It's amazing what dramatic music, a great voice over and a quote from Al Gore can do. I'm sorry this is so silly.

Well, I shut it down and then a service called LMGRD crashed and terminated. I guess it depended on nilm.exe running or something. Well it doesn't matter really because my LabVIEW still runs without problems. Thanks rolfk!

QUOTE (rolfk @ Mar 29 2008, 02:55 AM) And how exactly do I shut this crap down?

Does anyone know why the nilm.exe process is hogging my CPU?

I think sara and yasmeen85 are doing fine. Any issues should be addressed via the "report" button. See this reminder: http://forums.lavag.org/Forum-guideline-vi...der-t10455.html

QUOTE (Omar Mussa @ Mar 28 2008, 10:37 AM) Don't give NI any ideas. They might use it to get us out of the exhibition hall early to save on beer and food.

QUOTE (PaulG. @ Mar 21 2008, 11:35 AM) Don't be skeptical, just accept the fact that at some point the company will have to figure out a monetization model. However it's possible to use advertizing to fund the service and keep it free. It depends. We all use tons of Google tools in our daily lives and it's still free for me. Even if Google charges me at some point, i've had so many years of using a great product that I won't regret it.

QUOTE Well, it seems that you already have implemented a backup plan for this because if the path doesn't exist you revert to the fixed path right? So do the same. Ideally, the build should fail with a descriptive error because I've had many time where I have built something only to scratch my head when the output is missing. Then I realize thet the builder created the entire hierarchy of paths to the build out put in the WRONG location. However, the scenario you describe is a very rare case. Most developers I know work with a source folder NOT a single project file. Moving the project file is bad. Typicaly you would move your project folder. In my example, this is the "subfolder". The main thing is that NI's definition of relative falls outside the typical understanding. The destination is NOT relative to the project file regardless of how you spin it. It's a non-standard handling. The other option is to allow the user to enter a relative path themselves in the form "..\..\..\builds" and the problem is solved. No sweat of NI's back.

I just tried this. It's freakin' awesome! I'm hooked.

So just to check. Should I create a User Interface category for the Gallery?... and if I do, I expect a "surge" of new images right?

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.

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: