Leaderboard

Hi, I'm working with a PXI chassis and it's definatly something you wanna use... Teststand may also be usefull. I understand you're CLD, so maybe you should ask for training in order to become CLA. Reguards, Rodéric

Forget about the clearence for now. Instead work on getting good enough to start holding "Thursday Night Beer and Study Night" where you teach others. When the people behind the locked door realize you are an assest, you may get the invitation you are looking for. Ben

It costs thousands of dollars to process a clearance, and this cost is borne by the employer. I doubt you'll have much luck trying to get a clearance for a consulting gig. Plus your employer is probably not stupid. If you ask for a clearance when you don't need one, it will be obvious that you want it to help you go look for another job. Maybe you can just ask for a salary boost more challenges and skip the need to moonlight.

I'm not so sure about the secutiry clearance, unless you want to actively pursue work within an organization that requires it - I assume you already have the most often required clearance: ITAR. Also, as Ben said, security clearance isn't easy to get - and you'd need to convince your current comapny that you need it to execute your job. I'd take a good strong look at TestStand and PXI. ...and, since your profile lists your LabVIEW version as 8.6, I'd start playing around with the latest version.

I think I just wasted 43 seconds trying figure out which one was the sister. Ben

Here we have 2 brothers and one sister: 3dex.vi

#1 Security clearence. We have a shop locally that I call a "black hole" since every engineer or scientist that crosses over that event horizon is never seen again outside the fence. Getting clearences these days is not easy. If you have one already, you have a leg up. Ben

Like AQ said - children of the same parent are independent. You shouldn't think about SceneObjects as about real objects. they are rather nodes. Not all of them must have visual representation (Drawable). There is one node which is a "root" ant it may not be transformed at all, neither be tighten to any visual object. All other objects are its children (not necessarily directly). If you want to make group of objects move together, or share some properties, just create a common parent for them. You should also differentiate transformations from changing properties. Transformation is only geometrical movement (translation, rotation and scale). Changing color to blue is only changing the color property. Transformation of parent object always transforms children as well (however all transformations are relative, so it is only a kind of visual impression). Most properties of nodes along with their actual possible values have one called "Inherited" and usually it is a default value for new nodes. It means that actual value of certain property will always be the same as for its parent. This is why you observed changing colors for all the spheres.

A lot of folks are on vacation at the moment... you may get a better answer if you repost after New Years. You should be able to start with a top level object like a Canvas or somesuch and add multiple objects to it. So although visual objects always have a tree with a single root object, that visual tree is a tree, with arbitrary branching, not just a linear list of parent->child->grandchild.