Michael Aivaliotis

I would like to be able to remove an element from the register for events callback node.

Whenever the dependency list is updated, the project changes.

Also, don't forget: http://labviewmastery.com

QUOTE(torekp @ Oct 9 2007, 04:40 AM) Just in case? Just in case of what? What will happen if it's not re-entrant? QUOTE(torekp @ Oct 9 2007, 04:40 AM) ...Say I've got a mid-level VI that opens a connection to an Oracle database, reads a table, and closes the connection, and I use this mid-level VI all over the place. Make it re-entrant? How does it work now? Is it broken? I would assume the answer is no. Everything works just fine doesn't it? Re-entrancy is overated. In fact, it may make break a perfectly working program. Normal (non re-entrant) VI's provide Mutexing for free. Most people forget this and end up adding a lot more code to get something that a standard VI provides for free. My rule of thumb is, don't use reentrant VI's unless you are having serious timing issues with parallel processes waiting too long to access a common VI. There are also other use case that can only be done with re-entrant VI's. For example recursion, cloned front panels etc. other uses are common subVI's used in XControls. QUOTE(torekp @ Oct 9 2007, 04:40 AM) In general: any good rules of thumb, not already contained in the aforementioned wiki, would be appreciated. Reminder to all. If you participate in a forum thread and realize that something you are discussing should go on the LabVIEW Wiki, then put it in the LabVIEW Wiki. Even if it's incomplete, others will fill in the gaps.

That's mean Chris. That freakin' video's on a loop... Of course the population keeps decreasing, so it kinda gives you some hope that it will end somewhere...

I hope they consider some of the other things on my list... http://forums.lavag.org/New-8x-application...tter-t4172.html

Is that an Easter egg where you have to look at it cross-eyed and you see 3D images or something? They're called stereograms.

Here's the VI, bonus to whoever figures it out... and yes, it works as expected. The caller will be broken if this output is not wired.

QUOTE(Jim Kring @ Oct 6 2007, 12:11 PM) I agree... more cow bell.

Ya, this is a great feature in 8.5 eh?

What's wrong with this picture?

Ah Jim, you spoiled the fun. I wanted to see how far Justin was going to get with his reverse engineering...

You scared me there for a moment. I thought this was implemented already...

Karl - Excellent suggestion. This seems like the best way to go...

The user interfaces I build only have one button on them, and that one is pre-pushed.

QUOTE(dthomson @ Oct 4 2007, 09:30 AM) Dude, I wouldn't trust anything. This worked for me, but NI drivers and installation code is unpredictable. Meaning that some subcomponent MAY still point to the old stuff. You can never be certain. Let's put it this way, you don't have much choice in the matter...

Sorry, it got dropped during my crazy upgrade process. I will put it back tonight. Thank you for mentioning it.

Just to remind all of you about the recent procedure compiled on the LabVIEW Wiki (See: LabVIEW Bug Reporting). All bugs submitted to the LAVA LabVIEW bug forums must have a CAR# associated with them. If they don't, they will be move out of those forums. This will apply, moving forward to the LabVIEW 8.5 bug forum.

Sorry, no progress on this issue. It's still a @% pain in the buttocks. The solution for me is to upgrade to the latest driver and restart the build. So now it asks for a CD I have. The way this feature works is pretty ridiculous and needs to be fixed. There MUST be a way to tell the builder what msi files we want.

QUOTE(Aristos Queue @ Oct 3 2007, 11:28 AM) I don't believe it! Stephen actually admitted that LabVIEW is not perfect.

Don't have a solution for you but... It is probably a path somewhere that is absolute rather than relative. Check your build script. Maybe something there. BTW, are you using shared variables? I read somewhere of an issue with these in regards to absolute paths.

To edit the contents you have to click on the cell and wait... for a few seconds... the field will change to edit mode. On the last example you attached, you didn't have any data in your cells AND you didn't have editing enabled.

Ya, I tested it too. It works fine. The problem is that you didn't have any data in your cells AND you didn't have editing enabled.

Here's a nice trick for those that don't use (or ever will use) the grid. Every time you work on a VI, change the grid settings in the VI properties to some crazy out of this world value. Then sit back and listen to the screams comming from the neighboring cubicals...

Has anyone tried to use the new Unzip.vi? Everytime I run it, it just unzips the first file in the zip file then errors out with: Error code 2, System Exec.vi. Command was "touch 01191235142006 "filename"". Preview mode seems to work fine.