Michael Aivaliotis

QUOTE(TG @ Oct 20 2007, 04:22 PM) This is why I spent a weekend a while back compiling this http://wiki.lavag.org/tips' and tricks" title='LabVIEW Wiki article on tips and tricks' alt='Wiki article on tips and tricks' style="border-bottom: 1px dotted #3366BB; color: #3366BB; cursor:pointer; text-decoration:none;" class="wiki">tips and tricks page. This is the whole point of the Wiki.

I've added Hebrew to the language list. The next step is to create a dedicated language sub-forum. The biggest step is actually to get the word out to everyone who speaks Hebrew so they can find this forum. That's where the work is. If you feel strongly about it and help then that would be the next step...

QUOTE(Norm Kirchner @ Oct 19 2007, 05:51 AM) You guys have to stop thinking that way. You want something, build it yourself. You could probably crank out something in a few weeks that would take NI several years to release. Do whatever you have to do to make your life easier.

QUOTE(Norm Kirchner @ Oct 19 2007, 05:51 AM) You guys have to stop thinking that way. You want something, build it yourself. You could probably crank out something in a few weeks that would take NI several years to release. Do whatever you have to do to make your life easier.

This offer is now ended. Only Premium Members can change their name moving forward.

http://www.labviewjobs.com/ http://www.justtestjobs.com/

File a bug report with NI.

So I split out these topics into another thread so I don't hijack the original discussion. QUOTE(tcplomp @ Oct 18 2007, 09:21 PM) Basically, my thoughts are that you will probably have much larger bandwidth capability by placing the code on sourceforge. Also, getting SVN running on the LAVA server will probably take several weekends and is not something i am going to enjoy. I suggest just a forum called: "CR in-developement" which will have threads for various code projects. The first post of each thread can have a link to the SVN repository info on sourceforge. The nice thing about LAVA is that we are reaching a nice critical mass. Discussions are alive and exciting here. We've created a pretty decent community and I think we can get a lot done. It took five years to reach this level of involvement and I don't want to break the flow by telling everyone that they now must go use the weak Sourceforge forum tools for discussions. You can have the code on the sourceforge SVN for development but keep the discussions here on LAVA. only the released versions should go in the Code Repository after development has reached a stage for release.

I have an idea. Should we move this thread and other potential CR candidates to a special "CR in-development" area to better facilitate this? I think there is enough momentum here to justify this. After a bunch of thrashing, we can produce some decent CR code. Thoughts?

I have an idea. Should we move this thread and other potential CR candidates to a special "CR in-development" area to better facilitate this? I think there is enough momentum here to justify this. After a bunch of thrashing, we can produce some decent CR code. Thoughts?

You mean these? Download File:post-2-1192736521.zip Qualified Name Array To Single String.vi takes a VI's qualified name, given as an array of strings, and converts it to a single colon-delimited string. This VI may be useful for working with VIs owned by any library type, and it is used as a subVI of the other two VIs in this .zip file. Is This Control Of This LabVIEW Class.vi takes a control refnum and a LabVIEW class refnum and tells whether the control is an instance of the given LabVIEW class. It returns true for regular class controls/indicators and for XControls of the class. Is This Control Of LabVIEW Object Class.vi is the same as the previous, except it does not take a class refnum for input. LabVIEW Object is the built-in class that is the ancestor of all other LabVIEW classes, and this VI specifically checks to see if the given control is an instance of this class.

QUOTE(Yen @ Oct 18 2007, 11:50 AM) If you see a search result that is threaded then please forward the link to me in a PM. This isn't suppose to happen.

I have a better idea. Why doesn't someone start a wiki article that answers this question since it's been the 1000th time someone has asked this on the forums. We currently have a calling a VI category which has bits and pieces but no one comprehensive article. There realy is many ways to call a VI let us list the ways and what are the differences. An overview article is really necessary here.

QUOTE(neB @ Oct 18 2007, 03:54 AM) I never said it wasn't funny.

QUOTE(silmaril @ Oct 18 2007, 04:46 AM) Sure, and probably some time after that you will see LV 9.0. Oh and probably sometime after that you will see 9.1 then 9.1.1 then 10.0 then... So?

Threaded and outline mode was removed because it causes more problems to 95% of the people than the benefit it offered the few that liked it.

QUOTE(angel33 @ Oct 17 2007, 11:42 AM) Welcome to the forums, but what's with the attached image? You can't possibly think that's friendly.

QUOTE(Dean Mills @ Oct 15 2007, 01:34 PM) Many say that I have a God-like http://en.wikipedia.org/wiki/Omnipresence' target="_blank">omnipresence. That's not true. It just appears that way.

QUOTE(Justin Goeres @ Oct 16 2007, 11:17 AM) I prefer at least to always remind everyone that the 24MB run-time works just fine thank you.

I would recommend this for a Code Repository candidate. Please consider.

QUOTE(Darren @ Oct 15 2007, 12:09 PM) Using the Register Event Callback node.

Ok, this may be a bug, I (or LabVIEW) may be retarted, or fill in the blank. How do you debug callback VI's? I assumed that you could just put a breakpoint in the callback VI and the instance would break, but it doesn't. Any ideas?

It never ceases to amaze me where LAVA threads end up... but still, looking for LAVA lurkers out there. Just post and say Hi.

QUOTE(crelf @ Oct 15 2007, 10:18 AM) crelf, you're talking to an NI employee. They don't work like system integrators.