Michael Aivaliotis

Take a look at this. It should help you with your problem: http://vishots.com/005-visv-labview-class-factory-pattern/

Native LVOOP is Goop4? I haven't heard that term. Just checking.

There are strategies for this. You can release small and gradual until full capacity. People get cocky, and they ignore obvious signs. I'm a fan of releasing early and often. Yearly monolithic release cycles are big, scary and should be avoided. But hey, that's how most are used to working. Microsoft is going to release Windows 10 with frequent updates for free. But if you're a corporate user and want no updates, you have to pay.

So basically what you're saying is that we need to let an arbitrary length of time pass between making software changes and releasing it to the public. But we can't find out if the changes caused problems unless we release it to the public. - What does time give you? More testing? If you cut corners at the last minute to squeeze in a fix, then I can see it as a problem. But if you follow the same process, what's the harm? All software has bugs. It really depends on how rigorous your internal and external testing is. Having a public open beta or some kind of user involvement helps. It's also important to have a fast turnaround process on releasing new versions when a bug is found in the wild. Isn't that what "F" patches are for?

Filipe mentioned that it works on the Yun. I encourage you to check it out. it has built-in ethernet and wifi as well and Linux.

Hey folks. The issue that Hooovahh reported to me was that some tables in the mysql database got corrupted. Doing a simple repair on them fixed the issue. The server is fully managed. I just sent a support ticket to the server hosting company and they quickly fixed it. Now the current issue may be related to resource starvation during peak loads. There's a slider I can adjust; more resources = more money. I will slide it up one notch to see if it solves the problem. I looked at the resource usage for the past few weeks and it seems that there was a few times where the server hit the limit on Ram usage. Maybe that was the cause. Who knows. If you still see the issue, report it here with a screenshot so I can get the hosting company involved.

How about fixing it for Mac OSX? https://lavag.org/topic/16662-macbin-resource-file-info-core-generating-error-on-mac-osx/#entry102203

That demo was great. Will this work on LabVIEW for Mac? If not, I think it should be on the roadmap. But not critical for first release.

It doesn't require the NI C code generator toolkit. This is how the cost is kept low I am too, excited about this.

This is great ouadji. i made it a featured download on the CR.

I'm starting to use bookmarks more and more these days. I just wish it were more efficient. It hinders me rather than helps me. The concept and idea is great but the execution is bad. We need more tools from NI to help us develop and manage our workflow more efficiently. - still waiting. But to your question. Ya, breaking code to force a broken arrow that you have to follow, is common practice. You're not the only one. However committing broken code to the repo in a team environment is not recommended. It will cause some conflicts, and not the code development kind.

This assumes you have an ftp server running on your local machine, right? That's what 127.0.0.1 implies. In any case, error 7 is always a file not found error. So probably the path to the local file is wrong.

This thread made me LOL.

Just a small Christmas present to the community. You'll notice that LAVA is now running from an https URL instead of http. You shouldn't notice any difference in behaviour. But if you do, let me know. If you are using images in your signature. Please link to the https versions. You can use the lava gallery to host your image. Enjoy. PS. Some topic threads may give you a mixed content warning. This is because some of you embed remote images.

I just upgraded the LAVA server, so the response should be even better than the already pretty fast previous server. Enjoy.

i updated it.

Please go here for more info. We need the support of all CLAs. Here's your chance to be heard. Shape the CLA Summit, get recognition and spread knowledge among the community. If you don't have access to the forum there then please request to be added if you're a CLA.

Ok ladies. I did a VI Shots episode where I went through and mentioned some of the new features in LabVIEW 2014. Feel free to watch it at your leisure. However, during the show, I tried to demo the Reviewing and Updating Type Definition Instances dialog and it was a complete failure. Here is a link to jump directly to the demo. watch and cry as i repeatedly bang my head against the LabVIEW wall of shame. I made sure that before the show I tried out the demo and it worked as advertized. However, it didn't work live. I consider myself a smart guy but my wife claims otherwise. Am I just misunderstanding the feature? Can you take a look and point out what I did wrong? I just tried this again with various scenarios using front panel controls, constants with various datatypes but have not been able to trigger the resolve conflict dialog. Can someone translate NI's unhelpful documentation?

It was all merged into that forum. Nothing was removed.

It's still around, moved here: http://lavag.org/forum/17-vi-scripting/