MikaelH

Nice Work. //Mike

When the Application builder renames VIs and X-Controls, the X-Control gets locked as soon as the VI using it gets loaded into memory. So my guess this feature or another hidden feature is used to be able to modified/rename locked items.

My guess is to be able to build exe-files containing x-controls.

If you email goop@symbio.com they will help you, or just PM me you license key number and I'll have a look.

I can see the need of this, but since I try to keep classes small-ish, I normally remember that I should always access that attribute through the public/private helping method. But I still prefer referenced object and I can easily solve this with that design :-)

Your are right, these VIs should have some filtering functions. E.g. All controls/indicators where the Label Name starts/ends with a certaing character "...$". Or just have an array of controls refs and only use thoses. //Mike

I normally just use the OpenG VIs:

FYI my IT department blocked all my file uploads a while back, and I had to request special permission to be able to upload stuff to lavag.org.

I just got my result back from my CLA-R, and I passed , but not with 100% :-( I really like to now what questions I missed/missunderstood. I didn't find any questions that difficult, but you need to know the software development modules NI is referring to, you can find all that in the Self Pace training. You need to know the advanced stuff and limitiations of about X-Controls and classes.

The Control & Simulation Loop, has a solution for this: Last post for me this year, happy holidays everyone :-)

Intel has the solution for you :-) http://www.youtube.com/watch?v=U6IvsZnPtsY&feature=youtube_gdata_player&wapkw=smallest

Remember that a Static attribute using e.g. Globals/Functional Global in a base class gets shared between two different sub classes. That might be something you want, but maybe you want this “global variable” to have one unique value per base or sub class. In that case you can use a Named single element queue, using the object's class name.

GDS's GOOP3/4 class type have support for this. You can look at those implementation to get ideas of different ways of doing this. //Mike

FYI it's easy to reproduce: Using the Conditional Indexing output in a for loop with the TimeStamp type. Then activate the parallelism on the loop.

Remeber that property nodes causes a switch to the UI thread, they can be 1000 times slower than a local variable. //Mike

So you got a real cube, so nice

Our real code is not exactly like this, but we'll try this and see it it fixes the issue.

You need to use a Null Modem Cable. (pin 2 and 3 needs to be crossed). After that is should work. //Mike

If you use a PNG image you can get nice alpha-transparency on your front panel.

Thanks, then I just let my local NI office know that the CAR if filed

Thanks, I'm using 2012f3, I guess I have to wait for SP1 get see this fixed. //MIke

If I enable the Loop Parallelism on the this for loop I get this error: Do you get the same? compile_error.vi I'm going to report this to NI Australia. //Mike

Ahhh, now I get it , stupid me.

Can you give us a bit more info? What numbers, I32,SGL,DBL? Arary Size? Start Number?