Michael Aivaliotis

This is pretty much what the User Interface forum is for. We also have an XControls category and a User Interface category in the CR. We also have User Interface Portal on the Wiki which includes content on XControls. If anyone has any techniques or ideas to contribute along these lines please use the above mentioned resources to post your content. Especially the Wiki.

QUOTE (professor_rumsdiegeige @ Apr 5 2008, 03:55 AM) No, you should use shift-registers.

QUOTE (neB @ Apr 3 2008, 06:31 AM) Ya, those damn Applications Engineers...

I feel old and grumpy.

QUOTE (PaulG. @ Apr 2 2008, 12:38 PM) Kicking the AI seems to be a common human reaction. Watch one of my videos on VI Shots of Anybots. There's a clip in there where Trevor Blackwell gives Monty a kick. Also, watch this other one where at the end I actually asked David Hanson about how we should be treating our robots. He's a pioneer in humanoid interaction.

This issue is closed due to the online users list is not available anymore on LAVA since many months now.

Update: I passed this over to Invision support. It might be a bug. They're looking into it.

QUOTE (Cmal @ Apr 1 2008, 10:19 AM) Wholly crap I nearly spewed my drink all over my computer. :laugh:

I never use subroutine priority. I would like to see some benchmarking. Like many things in LabVIEW, such as thread priorities, the benefits of playing with them are highly overrated.

The problem is that people don't use anchor text in their posts. Instead of using friendly text they post the whole thing. The above URL should be posted like this. Notice that I used the word "this" as my anchor, NOT the entire URL. Let me spare you the the thought process. YES, I AM blaming all the LAVA forum members for this problem and NOT the RSS generator. PS. I'll look into it...

QUOTE (TobyD @ Mar 31 2008, 09:42 AM) Known issue, thanks.

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.