Jump to content

Michael Aivaliotis

Administrators
  • Posts

    6,196
  • Joined

  • Last visited

  • Days Won

    104

Posts posted by Michael Aivaliotis

  1. Warning! Beware of Language Content! Use Headphones... ;)

    She offends me and turns me on at the same time...

    <object width="425" height="350"><param name="movie" value="

    http://www.youtube.com/watch?v=cVv4ng2Ya44"></param><param'>http://www.youtube.com/watch?v=cVv4ng2Ya44"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/watch?v=cVv4ng2Ya44" type="application/x-shockwave-flash" wmode="transparent" width="425" height="350"></embed></object>

    <object width="425" height="350"><param name="movie" value="

    name="wmode" value="transparent"></param><embed src="
    type="application/x-shockwave-flash" wmode="transparent" width="425" height="350"></embed></object>

    I think we've found our NIWeek 2007 Keynote speaker.

    These videos are so full of awesome quotes. Where to start...

    I gotta go launch my rocket!

  2. QUOTE(Gary Rubin @ Apr 28 2007, 06:26 PM)

    Everyone is welcome here as far as I'm concerned. People already know that this website is called LAVA and what the two A's stand for. Perhaps they all want to learn from the experts, I know that's what I'm here for. I'm always learning something.

    QUOTE(PaulG. @ Apr 28 2007, 08:01 PM)

    If the more active senior-level developers spent half as much time explaining "X-Controls, point A to point B", "X-Controls, point B to point C" or "The Joys and Evils of SVN" or "How I learned to Stop Worrying and Love Variants" as they do responding to Nulll's and Sally's we would be a lot better off - and it would really reduce the "snob" level I pick up here.

    I agree with you on this. I have always been open about sharing my knowledge about LabVIEW. I have put on countless presentations at various LAVA meetings because I truly believe that we should all be programming at the same advanced level. Those that think LabVIEW is not powerful or cannot do this or that, think that way because no-one has shown them the light. We all need to give up our secrets for the common good.

    QUOTE(PaulG. @ Apr 28 2007, 08:01 PM)

    I can't help but feel a little intimidated myself. I know a small handful of hard-core
    LV
    developers who can write kick-arse code in their sleep.
    :)
    But even some of them couldn't tell me the slightest thing about an X-control or when/where/why to use a Variant. I count on this place to explain stuff like this to me. This is a great forum ... but it has been heading in a downward direction lately. Have we forgotten why we are here?

    Yes, it's about getting at the root of the feature or technology and figuring out "why the hell should I use this, and why should I care". One of the reasons I started the Wiki section of the site is for this reason. There, we have more time and can focus on explaining features and how to use them in various use cases.

  3. Recent posts have been downright mean! If you don't think the topic is worthy of your time or effort to respond then move along. You don't have to respond. Especially not with a smart ass remark that just makes you feel better. Veterans around here lately seem to be ganging up on new members in the same way schoolyard bullies do. Yes people, we know you're ace LabVIEW Guru's and it seems very silly for someone to be asking: "How do I get a VI to pop-up when I click a button". Well, I was in the same position when I started LabVIEW. It took me 3 months of development before I found out how to do this simple thing myself! In the end, my company hired an Alliance Member to come in a show me this and other tricks. I only wish I had something like LAVA back then.

    What are you doing to help? Why not write a Wiki article describing how to do this? Why stop there? Write an article on all of the issues plaguing new users. I am appalled at the tone and treatment of new members and those where English is not their first language. It's unfortunate that LabVIEW is not a very popular language since those members cannot find help in their native tongue and so resort to joining English forums for help. It is what it is. If in doubt, ask probing questions, get to the root of the issue. Be constructive and helpful. If not, don't respond! Please.

    It used to be that, if you were a LabVIEW user among users, there was a certain bond. Others would help you overcome hurdles and get you hooked on LabVIEW. What ever happened to that?

  4. QUOTE(Jim Kring @ Apr 20 2007, 10:06 AM)
    You should be forewarned that this is not just a place for you to get answers to your questions.
    I agree that LAVA is a lot more than "answers to questions", however let's not scare those that want to ask questions. Questions are perfectly fine and acceptable here as long as you are not a homework hustler (HH) - A student that tries to get solutions to homework questions.
  5. QUOTE(Eugen Graf @ Apr 17 2007, 07:55 AM)

    Your code does not make sense:

    1. In the top event structure, you are generating a user event.
    2. The bottom event structure responds to this and executes the <Command> case.
    3. The top loop is ALSO registered for the same event. It ALSO responds to the same event however it's too late, the message has already been removed from the queue from the bottom event structure. It then just iterates a timeout.

    What is the purpose of your design? Multiple recipients? If so, then you need to use a different approach. See attached image:

    QUOTE(Tomi Maila @ Apr 17 2007, 07:58 AM)

    :)

    Agreed.

    QUOTE(Eugen Graf @ Apr 17 2007, 08:23 AM)

    And I know too, that two event structures in one VI have to be avoided.

    This is not true. You can have multiple event structures without problems as long as they are not using the same event registration refnum.

    QUOTE(Eugen Graf @ Apr 17 2007, 08:23 AM)

    Another option is to create the user events in the main task VI and pass this to the other tasks, however register the events at the task level.

    QUOTE(Eugen Graf @ Apr 17 2007, 08:36 AM)

    P.S. firstly I wanted to replace Queues in tasks with User Events, because I have this problem:

    How do you think, what is better to use Queues or User Events? What is faster and eats less memory?

    You are presenting multiple issues here. Are you trying to get speed and less memory, or are you trying to solve your problem? The reason I'm asking is because you don't need to switch to a completely different architecture to solve your problem. Queues are pretty powerful on their own and still viable for your situation. From what I can see, your problem is that you are mixing your communication mechanisms. Why use "Set Value Property" on top of queues? You already have the pipeline so utilize it. See:

  6. Just want to apologize to all for the latest server outage. This was purely my fault and not due to any hack\crash or anything of the sort. Apparently, when you tell the server software to create a backup of all your domains on a daily basis, it does what you tell it... until your hard drive fills up! How nice! :headbang:

  7. QUOTE(Jim Kring @ Apr 13 2007, 11:37 AM)
    the software service providers that provide the best service to their customers and treat them well will win (I hope).
    None of the bugs I cared about were fixed in 8.2.1. as indicated from the NI buglist. So NI has dissapointed me with the 8.2.1 release. Am I being selfish? Of course I am... I'm a customer.
×
×
  • Create New...

Important Information

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