MikaelH

We have released GOOP Development Suite 4.7 The main things are: [*]LabVIEW 2013 support [*]The creation of Property Node methods. [*]UML Modeller fixes for analysing Actor Framework classes Download it from www.symbio.com/goop ...or here: GDS 4.7 LV2010 GDS 4.7 LV2010-64 GDS 4.7 LV2011 GDS 4.7 LV2011-64 GDS 4.7 LV2012 GDS 4.7 LV2012-64 GDS 4.7 LV2013 GDS 4.7 LV2013-64 And here are some videos: GDS(4.5) Features Video Other Videos Contatct goop@symbio.com for questions. Thanks, Lars Persson and Mikael Holmström Symbio Sweden

FYI I have now (since I'm using LV2012 SP1), recently converted all our shared company code/drivers to save the VIs again without Compiled Code. So far no problem. I just ran this VI overnight, and committed everything the morning after.

Hi Bjarne It's a LV2013 limitation, that I have fixed in GDS 4.7 We're doing the official release this week. But you can download the beta version from here: http://goop.endevo.net/GDS/GDS_4.7(R1U)_2010.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2010-64.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2011.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2011-64.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2012.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2012-64.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2013.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2013-64.zip Cheers, Mike

I’m sure it’s not just me that missed out the change in LV 2013, when it comes to Sub Panel’s Insert VI method. From 2013, you can't insert ctl-file any more. For me that is a show stopper right now. So I can’t upgrade to 2013. Can anybody at NI let us know, why this support was dropped, and what the work around would be for my exe file that currently opens CTL files and shows then in a sub panel?

Here are the latest GDS builds http://goop.endevo.net/GDS/GDS_4.7(R1U)_2010.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2010-64.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2011.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2011-64.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2012.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2012-64.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2013.zip http://goop.endevo.net/GDS/GDS_4.7(R1U)_2013-64.zip If these pass the testing, we'll rename them and release them as GDS 4.7 Cheers, Mike

You should be able to download it from symbio.com/goop (on the lower right side) But I'm about to release GDS 4.7, this version should be downloadable in the end on this week. I'll keep you posted. GDS 4.6 don't have to many exciting stuff, other than 2013 compatible. GDS 4.7 have a 2013 bug fix and also property node creation (so you can access your object data through property nodes) Cheers, Mike

Maybe a temporary file that is read when the State object is created. If the state has not been interupted it will delete the file so when created next time, the State object attribute will be using the default values.

Thanks Michael, really appreciated

It looks good. BTW in GOOP4 we decided to make the object attribute protected. That means you can use your parent’s GetAttribute VI(s) in your child methods.

Hi Helcio You are getting closer and closer ;-) Everything looks good, but when you like to update the Number Of Timers that you store in the class attribute. Make sure you do that inside the same IPE structure. So do it something like this. And also, you don't need (and shouldn't), wire the Class Ref input to the Create method. This input is only used by the framework when you inherit a base class. Try to create an extended Timer and inherit it from your Timer class

Or could the table be replaced by a picture control :-) It was nice to see you too. Cheers, Mike

Remember that the Object Attribute is unique to the wire coming out of Create. If you want to know the number of Timers created totally of one class, you have to either use Class Attributes (Add that Design Pattern to the class). Or you have to name the object and share the same object. Do you know how Class Attribute works, or should I create an example for you? BTW there is a bug, if you add the Debugger/Persistent Design pattern to the class (but you are not in this case), for LV 2013. This bug is being solved and GDS 4.7 will soon be released. Oops, I saw another thing; you are mixing by value and by reference in this class. You probably would like to go with By Reference in a class like this. Be sure you don’t modify the Class Private Data with the attributes you have done, move them into the file: ObjectAttributes.ctl, and use the IPE-Structure to modify them.

..or just use the old nice Picture control, lot of fun work though :-)

It sounds like your class has become to big manage. I've never had this requirement.

So the Method "GenerateNextX" belongs a class e.g. "Creator" class is that what you mean? If so the Creator class has a normal Association dependency to the Class "X" This is what Symbio's UML Modeller would show about that design. (select an assoication and press Shift to open the Context Help) Cheers, Mike

Symbio will give away 3 UML Architect GOOP Development Licences.

Lol, I don’t share needles, but objects from time to time. I still use reference objects in my designs, and I do share them in parallel loops when needed, but that is objects, not the data itself. See you in 2 weeks AQ :-)

I'm coming. See you guys there.

So I made a test application using roughly the same design as my real application. ActorTest1.zip And of course this works fine on both computers, I can spawn 50 Actors at the same time without any problem. I still might put in a small delay between the Launch of every actor just in case.

I did see this problem on the production machine which has 2 cores, but not seen it yet on my 4 core machine (but I haven't tried to run too many DUTs). I don't think it's an Actor related issue, I think it could be a "Reentrant,Fire & Forget(0xC0)", "Preallocated Clone" , "Queue Reference" - Problem. If I have time I'll create a test application to see if I can cause it to fail. It might be the production computer that has some problems.

I'm not, it's so strange, why can I run a few Actors in parallel but not too many?!? I might do a 2012-64bit version to see if that makes the Queue Reference work better.

Hi I have a very strange Actor Launch problem. I start an Actor to do some calculations for every attached DUT. And that has been working great, 1,2,3 Actors(DUTs) no problem. But now I’m starting to get problem when I have around 5 or more Actors that I start of the same type. The screenshot below shows my problem. The queue used to get the Actor’s Enqueuer back after the Asynchronous start of the Actor, didn’t receive anything. I debugged the code, and could see that the Queue-Reference was the same for the Enqueuer and the Dequeuer. Also no errors were found on the Enqueuer Error in. Has anybody seen something similar? The code only fails if there are too many started actors at the same time! Cheers, Mike

Guys, I did find a bug in the Sub VI, that has been fixed now. The "BDwin.Origin" position had to be inverted.

Is it just me that’s annoyed of the QD Insert item on wire function? If you have a diagram like this below, and you like to add a +1 here: The result becomes like this: Enough is enough, I can't live without this feature but I tweaked it so it actually works. Or at least it seem to work, please feel free to test it. Place the attached VI in the Plugin folder: ..resourcedialogQuickDropplugins Update the Insert.vi plugin and add this Sub VI here: Insert_GuessInsertPoint.vi (I've updated this sub VI) Did it work for you? Cheers, Mike