crelf

QUOTE(neB @ Jan 20 2008, 09:37 AM) I just had a few guys go through CLA for the first time, and their pass mark was set at 70.

QUOTE(neB @ Jan 18 2008, 08:34 AM) :thumbup: Nice work Ben!

Job Title: Senior Systems Engineer (Test Software and Integration Group) Company: VI Engineering :thumbup: Locations: Positions available in our Farmington Hills, MI, 48331 Office Salary/Wage: $YouTellMe - Based on Experience Status: Full Time, Employee Relevant Work Experience: 3 to 5+ Years Career Level: Intermediate to Experienced (Non-Manager) Education Level: Bachelor's Degree Residency/Citizenship: USA Citizenship or Greencard Required Driving Business Results through Test Engineering V I Engineering has a vision for every client we engage. That vision is to achieve on-time and on-budget program launch more efficiently that the competition. To realize this vision, customers need to achieve predictable test systems development, eliminate waste in test information management, and drive increased leverage of test assets. An underlying requirement for all of these areas is metrics tracking and measurement based decision making. Job Description Ready to make a difference? Bring your experiences and skills to the industry leading test organization where you can make a difference. Help us to change the way the world views test. We are seeking talented Systems Engineers to be responsible for technical execution of successful projects in the Military and Aerospace Industries. The position will have high visibility to customers and vendors. This is a very fast paced team with close customer contact and strong career development opportunities. Required LabVIEW National Instruments Hardware Experience in Design and Implementation of Test Software including integration Experience in ATE usage and development Experience in reviewing of Mechanical Fixtures Experience in understanding the design of Circuit Boards as they relate to a total system Experience in Requirements Reviewing and Design Creation Experience in Taking Part in Technical Teams throughout All Phases of Project Lifecycle Experience in Interfacing with Sub-vendors and Customers Ability to Multitask Comfortable Working on Various Team Sizes Excellent Communication Skills Experience executing verification and validation for projects Experience generating and/or reviewing cost proposals Desired TestStand LabVIEW-based Object Orientated Programming MS Project UML Experience with Projects for Regulated Industries Degree Technical degree (BS Engineering, Physics, Math, or similar) National Instruments Certification(s) a plus National Instruments Courses a plus Notes: Expected Travel Time is up to 25% Relocation assistance is possible. V I Engineering offers incredible opportunities to grow and advance your career, a dynamic work environment and the flexibility of a small company. Our team values innovation, out-of-the-box thinking, high-toys and a fun working environment. We're a National Instruments Select Integrator, and we're the closest you can get to playing with all the pre-released and new NI toys without joining the NI R&D team - and we get to play with them in the real world. Interested in joining our team? email us: jobs@viengineering.com

QUOTE(Nandha Handharu @ Jan 18 2008, 03:18 AM) Michael_Aivaliotis is one of our members (actually, he's the admin) who seems very interested in robotics - you should read his blog.

For some reason, the DataAct website keeps crashing my IE7 so I can't get a hold of them. I've been able to limp through and download the installer, but it only installs a few startup shortcuts (I'm using LabVIEW 8.2) - when I run the installer the "dqGOOP" selection is unchecked and disabled, so I'm struggling to install it. Can anyone help? Or, at least, let me know how ot get in contact with someone at DataAct without having to go through their website?

QUOTE(Yuri33 @ Jan 17 2008, 06:31 PM) Yes - you're absolutely correct. I was thinking of the mouse-up event (the one I use the most on UIs). Sorry for the confusion.

QUOTE(Neville D @ Jan 17 2008, 06:05 PM) :thumbup: I agree.

QUOTE(Aitor Solar @ Jan 17 2008, 03:32 PM) I know that (you said it in a preivous post): I wanted you to put it here too so that everything to do with your question resides here on LAVA, so that, in future versions of LabVIEW when that xcontrol might be gone, the thread doesn't date. It's not a big deal, so don't worry about it if you don't want to.

QUOTE(Yuri33 @ Jan 17 2008, 11:16 AM) Disabled controls will still trigger an event. That said, you can check if the control is disabled or not, and decide whether to execute the code as you're suggesting.

QUOTE(Aitor Solar @ Jan 17 2008, 10:37 AM) I meant include the xcontrol too.

QUOTE(Aitor Solar @ Jan 17 2008, 08:55 AM) Great - and yes, I agree: the only time it should change is when upgrading a VI from <8.0 to >=8.0.

QUOTE(Aitor Solar @ Jan 17 2008, 08:41 AM) Can you please post the code so we have it here for future reference?

:question: Did this ever get changed?

QUOTE(tcplomp @ Jan 17 2008, 12:19 AM) I can't say for sure, but maybe the check is applied to any version below the current one (?) So you should be able to create a new VI in 8.2 with a constant feeding a case structure, then open it in 8.5 and have it convert - but why? If you've got a constant feeding a case structure in 8.2 then it's going to act the same way as in 8.5. Intriguing - is anyone with 8.5 able to try it? I've attached an 8.2 example VI.

QUOTE(RagingGoblin @ Jan 17 2008, 04:16 AM) I know this is of little help, but your code looks fine to me - I think that you certainly *should* be able to do what you're trying to do...

QUOTE(Aristos Queue @ Jan 16 2008, 05:31 PM) Nah - he's more entertaining this way

QUOTE(Gabi1 @ Jan 16 2008, 11:37 AM) Just mouse-leave the item that's opened. QUOTE(Gabi1 @ Jan 16 2008, 11:37 AM) overall i like it as a curiose, but would hate programs that would even think of doing something without me telling them to do so I agree, but that's not what this is doing - you're telling it to do something by mousing-over it, rather than clicking on it. ...although this brings up an intersting issue: mouse hardware can be unpredicatable (especially those little touch-pad thingies) - when working on a laptop, then can whiz off to one side with no warning, and I don't think this no-clicking environment would be good in that case.

QUOTE(jzoller @ Jan 15 2008, 07:00 PM)

QUOTE(neB @ Jan 15 2008, 03:19 PM) It's not only part of it, it's often the best part! ...and I'm not trying to stiffle your contribution, but that doesn't mean I need to agree with it. What I don't agree is that telling a user "Just don't touch the mouse" doesn't seem at all productive.

QUOTE(neB @ Jan 15 2008, 02:49 PM) No - that's crazy talk, and I think you're missing the point: they are suggesting that the definition of "commit" change.What we're currently used to: select = mouse over the item commit = click on the item What they're suggesting: select = mouse over the item commit = mouse over the item next to it labelled "commit" I'm not saying that what they're suggesting is wrong or right, nor that's it's better or worse, but I'm certainly always open to new UI ideas, whether that's components or patterns.QUOTE(eaolson @ Jan 15 2008, 02:55 PM) I also don't like the fad of every sub-menu swooshing into view and then swooshing away when I'm done with it. (Macs, I'm looking at you.) It's disorienting, unnecessary, and time is spent waiting for the menu to finish animating into position. So you're not an auto-tool user, are you?

QUOTE(gmart @ Jan 15 2008, 02:00 PM) Well, their UI means that you can do what you're after. The way they've set it up means that soft commits (one's that you can eaily back out of, so it's really more of a "select" than a "commit") can be backed out of by moving the mouse out of the active area again, whereas hard commits (if you played with the interface for long enough, it asks you a question on whether you're okay with not clicking) require a "select" then a "commit" (by moving the mouse into the "yes" or "no" selection area and then moving into the "confirm" area). Confusing for us already comfortable with the way UIs work? Absolutely. Confusing for those new to computers? I'm not so sure.

QUOTE(Aristos Queue @ Jan 15 2008, 12:17 PM) The "mousewrap" frightens me. I'm all for UI design changes that map more closely into human nature - the problem is differentiating our conditioning with computers, UIs and input devices over the years from nature - the only way to get around this is to use computer virgins. That said, it takes a lot of research to determine real intuitiveness, and filtering out nurturing ain't easy. For example: when looking for someone in a crowd do you search, find and then engage, or do you search, find, select and then engage?

QUOTE(Gabi1 @ Jan 14 2008, 02:36 PM) I've only got what's http://forums.lavag.org/index.php?showtopic=9850&view=findpost&p=40294' target="_blank">in the list at this stage - I'll let everyone know if anything else gets added...

QUOTE(silmaril @ Jan 14 2008, 05:04 AM) Not bad, not bad at all. Although there's not much room for the back swing

PS: You can keep up with the NI hardware that I'm selling here: http://search.ebay.com/_W0QQsassZcrelf