Michael Aivaliotis

QUOTE(Val Brown @ Apr 30 2007, 05:26 PM) I don't mind working on this however, the requirements seem vague. The XControl should not actually implement any of the functionality. XControls are mainly for UI implementations. What does your data type look like? You say you want Stop, Play, Pause but you can just as easily assemble this inside a cluster typedef. One thing I can think of is a Play button that after being pressed, turns into a pause button. I think we should work on the requirements first: Must have a Play, Pause, FF, FR button Play button will turn to pause after it's pressed. Should have a progress indicator. Progress of what? Music? QUOTE(tcplomp @ Apr 30 2007, 06:17 AM) Yes it is kind of dissapointing only one XControl made it into the Code Repository. Dissapointing but not surprising. XControls are not easy to master. BTW, I'm giving an XControl presentation at NIWeek this year. Those that are afraid of XControls should attend.

Ok, it turns out that this is a preset program without any smarts to identify the proper movements. Just a movement experiment. Works well...

BTW, the woman next to her is her Mother!

QUOTE(xtaldaz @ Apr 30 2007, 10:58 AM) I think that's best. . Btw, is does your avatar happen to be a jackrabbit?

This is really nice. Not sure if the NXT is looking at the colours or just doing a preset routine. Excellent nonetheless.

Hey, I put a warning up... and I put it in the LAVA Lounge. Besides, I'm just trying to raise awareness. Tryin' to help the ladies out there...

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!

See Here: http://forums.lavag.org/Wiki-LAVA-Forum-Gu...ines-t7691.html Let's hash out the LAVA Bible.

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.

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?

Link to LabVIEW 8.2.1 Just use your given SN.

Please see here for information on how to attach and upload images into your LAVA posts.

QUOTE(hannibal @ Apr 21 2007, 12:14 PM) See here: http://forums.lavag.org/How-to-Insert-Images-in-your-Posts-t771.html' target="_blank">http://forums.lavag.org/How-to-Insert-Imag...Posts-t771.html

QUOTE(Jim Kring @ Apr 20 2007, 10:06 AM) 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.

QUOTE(Nullllll @ Apr 20 2007, 06:06 AM) If you know, then why ask? If you have the VI's in your palette then try them. What are you looking for?

What 3rd party program are we talkin' about here?

Try this for learning: LabVIEW Tutorials Lot's of stuff out there.

See my related post here: http://forums.lavag.org/index.php?s=&s...ost&p=28409

QUOTE(Eugen Graf @ Apr 18 2007, 06:35 AM) Are your devices, serial? I think only serial devices really need to be closed to release the port for others to use. GPIB devices don't have to be opened or closed. At least not anymore. Other than Visa Open or Visa Close, I'm not sure what kind of instrument command you want to send. Regardless. If this is still the case, you can do this with queues as well. Keep in mind that you will need different queues for different types of tasks. The example shown assumes that you are working with the instrument task queue: http://forums.lavag.org/index.php?act=attach&type=post&id=5545 http://forums.lavag.org/index.php?act=attach&type=post&id=5546 (LabVIEW 8.0) There are many solutions to your problem. User events can be used as well. However, I would even argue that you don't need parallel tasks anyway. Why can't you just do everything in the main state machine? I'm not sure of the benefit in your case. Perhaps data saving would be better off in parallel if you have lot's of data. What is the speed of the overall system?

QUOTE(JFM @ Apr 5 2007, 08:14 AM) Hmm, I think we should place some bets here. LAVA could use some donations . My money goes on the queue.

QUOTE(Eugen Graf @ Apr 17 2007, 07:55 AM) Your code does not make sense: In the top event structure, you are generating a user event. The bottom event structure responds to this and executes the <Command> case. 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: http://forums.lavag.org/index.php?act=attach&type=post&id=5543 QUOTE(Tomi Maila @ Apr 17 2007, 07:58 AM) Your upper loop is generating user events for itself in reponse to the same user events. This will not be very wise 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) The aim was to register all events in the main task and handle them in other tasks, I want to commit only the registration refnum to other tasks, but you say its not possible, I have to register events in each task. 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: http://forums.lavag.org/index.php?act=attach&type=post&id=5537 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: http://forums.lavag.org/index.php?act=attach&type=post&id=5544

QUOTE(Pablo Bleyer @ Apr 17 2007, 10:05 AM) We've just added a [wiki]Control References[/wiki] article on the http://wiki.lavag.org/' target="_blank">LabVIEW Wiki.

QUOTE(Aristos Queue @ Apr 15 2007, 05:33 PM) Yes, however I'm concerned about obfuscating the UI and diagram. How would you indicate the groupings?

Doing OOA&D on a coffee maker is a standard classroom topic used my many to teach the principles. Another one is a bank machine.

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: