Jump to content

Michael Aivaliotis

Administrators
  • Posts

    6,196
  • Joined

  • Last visited

  • Days Won

    104

Posts posted by Michael Aivaliotis

  1. QUOTE(jdunham @ Nov 15 2007, 05:42 PM)

    Do you have a conditional disable structure on the diagram or in a subvi? If you have changed the conditional symbol definition in your project, then the same VI could definitely be working inside the project but broken outside of it.

    No, it's not that.

  2. Not sure what causes this but I've experienced this several times lately.

    I run a toplevel VI several times and somewhere I get an error on the error cluster. So I decide to start debugging by opening up the subVI's. When I open one of the subVI's I notice that it has a broken run arrow and now I also notice that my toplevel VI has a broken run arrow. How is it possible for LabVIEW to run broken code? The only thing I can think of is that the broken code has not propogated to the current running application instance until I open it up. Not sure why however since I only have one instance. I have the project environment open too.

  3. QUOTE(Aristos Queue @ Nov 12 2007, 05:28 PM)

    Suppose I develop patentable work for NI. Under the terms of my employment, I get a fee when NI files for the patent and a second fee if the patent office approves the patent. And that's it. Is that reasonable? If the technology leads to a massive explosion of NI's income, should I get a share of that? We could have that debate all day.

    Or, how about you get a cut from every copy of LabVIEW sold because it contains some code you wrote. So If I write some text in a word processor, I'm a writer with certain rights, but If I write some text in a programming dev. environment, I have no rights. Hmmm. explain to me the difference...

  4. The contract is between film and TV producers and the Writers Guild of America. The writers already have a contract via the union walking in. The current contract does not cover online or portable media issues. The writers already get a cut from broadcast and film releases. The main issue is that the concept of "broadcast" is changing... What about youtube?

    I wonder if the idea of a LabVIEW programmers union has some traction... :D

  5. The people that brought you LAVA, the LabVIEW Wiki and the Code Repository have been working on helping you find targeted LabVIEW information on the web.

    We are announcing: LabVIEWSearch.com.

    This is a search engine that focuses on returning results only from a narrow collection of web resources that are LabVIEW related. It's amazing how much LabVIEW information is missed or buried in the noise of the web. LabVIEWSearch.com let's you cut through the noise and get the information you really want. The initial search is global to the entire LabVIEW ecosystem. After you get your results, you can narrow down your search further to specific sources or topics via custom links. Now you don't need to hop from one website to another. All the sites you know and love are searchable from one convenient location.

    Currently the search engine is in Beta. Please send questions, suggestions or problems to: info@labviewsearch.com

    You can also just reply to this topic.

  6. It was back in November of 2002 when I decided to start the LAVA website and forums. Brown? What was I thinking. :rolleyes: . I took LAVA, which started as the first independent advanced LabVIEW user group and then started hosting meetings myself. It was pretty awesome to meet with LabVIEW users outside of the traditional sales oriented framework of the NI funded meetings.

    post-2-1194754002.gif?width=400

    post-2-1194753985.png?width=400

    Well, the website and forums took off and is now the largest independent LabVIEW user community on the internet.

    Some stats:

    Average monthly new forum registrations

    In 2003: 15

    In 2007: 150

    Average new monthly forum topics and replies.

    In 2003: 20

    In 2007: 1800

    Total forum topic views since 2003: 6Million

    I don't have logged traffic stats since 2003. I just seriously started monitoring the LAVA traffic last year. Currently LAVA has 7,000 daily page views and growing.

    LAVA is here to stay. It's a place where LabVIEW users from all over the world congregate and NI can't control it. I like that part the best ;) . We have a great community of advanced LabVIEW talent. I'd like to thank every single one of the members who have stuck through thick and thin with all the various experiments the site has gone through. I'd also like to thank those that have decide to make LAVA their exclusive home. That's cool! Let's also not forget the contributions of a few hip National Instruments employees who are very active in the discussions.

    Currently, The focus on my end is the LabVIEW Wiki and the Code repository. I strongly believe in these venues and think that with your help we can make these (especially the wiki) the best LabVIEW resource out there. If the WoW wiki can have 48,000 articles then I think we can do better than 220. All pages on the Wiki are user editable by you and you can create any page you want as long as there is a connection to LabVIEW in some way. Did you know that you already have a personal page on the wiki?

    New community enhancements are on the way. What does the future hold? The future looks bright :thumbup: . What do you want to see in LAVA's future? Respond with your wish list.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.