ShaunR

I'm 100% with you here...ESPECIALLY the tree view..... - and my UI are "simple" (or they would/should be...lol). I went through a stage of writing front ends in another language and have only the backend IO and stuff in LV. I didn't find many downsides to this apart from my abhorrence to mixing languages. In fact I might play with it again but using TCPIP as the glue rather than DLL calls. Oooh. Epiphany This would mean the UI doesn't even have to be on the same machine

Only code monkeys need speed....for all the changes I want them to do I too like the new editors purely because you can import icons. It used to take me ages to try and make a new icon pixel-by-pixel...now I just import an image and (sometimes) make a box round it ...much quicker. Amen! Data-finder? What's that? Never used it. and If I ever decide to find out what it does I probably never will. NI device Monitor? I don't have any USB devices. NI PXI manager? Don't have a PXI rack., NI Motion Device Manager, NI WebServices.... et al. This is one of my pet peeves too. Along with the amount of coding that must be done just to make a UI work. Most projects I find nowadays are about 60% UI code and 40% real-stuff. The UI hasn't really changed much since the MAC original (in look and feel). No matter what you do. It always "looks" like LabVIEW. I think we would see many "new" looks if NI gave us access to the controls canvas and "onPaint" event..

Here's one from me then I wouldn't worry too much. If rep points could be taken away; I'm sure there'd be a minus sign in front of mine

You mean C++ ?

My version is set as you describe (yellow with a grey border for BD labels, LV 2009 and 10). My problem is that I can't remember how I did it an cannot change it back . But it is possible I'll have a play and see if I stumble across it again

I like the one in the red dress

I don't know how the JKI install works, but you are right. You only need to compile the hierarchy from the top level VI (which is what your VI tree is doing) rather than compile every VI.. I scan all VI's and see if they have any parents (lone VI's - these will be the top level VIs) then compile "Entire Hierarchy" only for those VIs and just save all the dependants. Opening a reference is quick, but compiling isn't. The advantage of this method is that you don't need a VI Tree VI (so it's more generic) and, for a couple of hundred VI's you only end up compiling a small subset and the compilation process is smart enough that shared VI's that are already compiled and/or saved are skipped (or so it seems) It's no really an issue in 2009 because it's all very quick. But 2010 is such a slug (installing SQLite API in 2009 takes about 20 seconds. In 2010 it's about 1 minute i.e 3x slower)

There's a few programmatic solutions on this thread

Check the ports in MAX. Labview gets its VISA information from it and it will have better diagnostics.

I've never used it....but a quick Google revealed that not only you have this (and similar) problems.

Version 1.3.1 released This is a purely a bug-fix release (addresses the bug reported by MarcA) and adds an installer. Upgrading to this version is optional..

Hmmm. I wasn't aware that mass compile skipped anything.It doesn't say anything about skipping in any logs when it comes across a password protected VI. Thats unfortunate. It means that a password protected VI is no more portable than a VI with the diagram removed. I had always thought of password protecting to be a better solution because having the diagram meant you could re-compile for different platforms/versions.

You could draw your own axis using the 2D picture plot functions (2D picture plot). The downside is you don't get all the zoom candy etc.

Indeed. But not really solution though. I'm hoping I'm just missing something obvious since the mass compile (and presumably the VIPM) can do it, however the mass compile only scans directories, rather than project trees.

How do you re-compile a password protected VI? I have a couple of VIs that are password protected, and a little tool that goes through a project, recompiles it and returns any errors and what they are (which then goes into a database) The mass compile copes with it no problem and simply compiling from 2009 to 2010 shouldn't be a security problem. But I can't find a way to do it. The open VI reference takes a password parameter so I presume you can't get a reference with that. And getting the reference from a project returns error 1040 (password protected) when the compile script node executes. Any ideas?

Deleted 'cos can't be bothered.

I would suggest replacing them in the palette (like the space constant '). I've been using my ones for over 10 years so it's not really a maintenance issue, I appreciate the thought, but really the primitives need to be changed.

+ 1 kudos. And while they're at it they can do the same with tick count, and wait next ms tick.

Well. NI also do counter timers. But it is's really a sledge hammer to crack a nut. Whenever I come across devices like I think you are describing, I always use a PIC to convert whatever in to RS485 and have a nice serial ascii value returned (you can even do stuff like streaming to the PC). Cost less than $5 a throw, much more reliable and has a huge saving on cabling in multi-device environments. And once you've done it once, you can use it on virtually any obnoxious interfaces with a bit of software tweaking.

RS422 is multi-drop and can be cabled for distances up to about 100meters.. You can have all your devices hanging off of one RS422 port (up to 12 or 16 if memory serves). If you can get all your devices with a RS422 interface then you won't need to mix and match with USB. Make sure, however, that the devices are really RS422 compliant. Some manufacturers say that they are 422 when really they are point-to-point but with RS422 line drivers (i.e not addressable). I highly recommend the NI RS422/485 cards. for the PC end.

May seem like a silly solution. But can't you put the data on the right hand side so as as the # columns grow; they grow away from the graph rather than towards it? Then you can keep the size fixed.

If only we had a "ping" function

Where? Behind that coffee machine?