Michael Aivaliotis

That's a good article. It covers all the aspects of building the cabinet. I have an old-school multi sync CRT myself. It really make s difference for authenticity. They really do weigh a ton.

What have you set in your options? You need to pick 'show me all content' NOT 'since my last visit'.

Before LVOOP, if you did a "find all instances" on a VI, the results would show up in under 1 second. This made "find all instances" a very useful tool to quickly navigate your code. Now if that same VI is a member of a class and is a dynamic dispatch parent or child, LV has to do a complete search of all the VIs in memory which takes forever if you have over a thousand VIs, which is typical on our projects.

I give reputation points to funny posts too.

Wow, that's awesome!

This post is just to update everyone on what's happened on LAVA since the initial Forums were setup after the crash. The forums has been through several upgrades. Each upgrade has fixed several bugs: Version 3.0.1 Version 3.0.2 Security Update 1 Security Update 2 I also ran a fix to solve the broken download links problem on the LAVA 1.0 content. I found and fixed about 450 broken links. These are links that pointed to nowhere. Unfortunately I can't easily fix the posts that refer to files but don't have links. The problem is I don't have the name of the attachment. I know approximately the group of files that could possibly be the ones but no idea which one unless I open each and every one in that group and see if it relates to the topic. This is a daunting task. Right now, just keep reporting those (with the "report this post" button) so at least we know which posts they are. We are also working on the RSS feed duplicates issue. The RSS feeds code was a modification that we paid to get implemented on top of the original code. It seems that it's a little buggy so we've asked the author to help fix this. I'll keep you posted. All the code repository submissions have been attributed to the correct authors and we have had some new submissions. Please continue to submit code and give feedback to the authors on their support threads so they can make improvements and fix bugs. The Gallery has had a bunch of photos from NIWeek09 and we have the user interface category back up and running. Please submit cool LabVIEW UIs there. Also don't forget that the LabVIEW Wiki is still operational. We still need help adding content.

Resolved.

Just want to let everyone know that we have an expert working on this right now so hopefully it will be resolved soon.

I think that if you uninstall it, VIPM restores the old version. I think that's how PJM_labview built the package.

Thanks. This is a very annoying bug.

Thanks Justin for that!

Try their website.

I'll be working on a "final solution" for all the broken download links soon.

I'll have to dig deeper into this over the weekend.

Where did you get this file from? Is this stored locally? This is not the current content from LAVA. The latest XML file can be retrieved from here.

This issue is now resolved. Everyone can report posts now. Admin edit: this post was reported successfully by Ton Plomp with the following text: "This is a test report"

I wonder if this is an outlook issue. As I said, not happening for me in Google Reader. Does deleting the item from outlook signal to outlook that it should retrieve it again next time? Doesn't make sense. RSS is just an updated XML file. It doesn't have a cache or any smarts. It just has the latest content. I'd like to see the XML file you are linking to with evidence that it contains duplicate entries.

Yes this issue is still present because those threads are probably being moved from the 1.0 forum to the 2.0 forum and somebody replied to it. It's not getting worse, it just depends on the number of old topics that have new replies. Once the full thread is received in your reader once, you should only see the new replies from then on, not the old ones anymore. I use Google reader and this is the behavior I see.

This is a feature.

Thanks I took care of it. I'm working on fixing the reporting problem. Already reported it to support. Awaiting response.

You can also create a case in your state machine called: "Update UI", then pull the values out using a "Get Data" Method. Then just write the data to the UI using local variables. I know that this may not cover all your scenarios, but it's the method I use most often. For some reason I feel dirty when I use control references.

Youtube Video: <object width="480" height="385"><param name="movie" value=" name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src=" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="385"></embed></object>

Just stumbled across this new feature in LV2009: Build Application from VI

I think everyone's missing the point of the DVR. The biggest benefit of the DVR, IMO, is the ability to use the IPE (In Place Element) structure to read write data. Using the structure provides exclusive lock to the data access AND eliminates copies. Doing this with a SEQ (Single element queue) is a PITA and requires a whole bunch of lock and unlock code. On top of that you create extra data copies when you read the queue element. Data Value Reference Read / Write Element Border Node