Jump to content

MikaelH

Members
  • Posts

    835
  • Joined

  • Last visited

  • Days Won

    49

Posts posted by MikaelH

  1. No sorry, it still don't rename the class controls/indicators.

     

    I suggest you change the names to Object In/Out or Reference In/Out on all you classes so you don't have to rename the label when you clone/rename the class.

     

     

    Regarding the crash, I've only seen a few crashes myself, but I do get it to hang from time to time (i.e. never finish the clone operation).

    But after restarting LV it works again without any problem.

     

    But I’ll test your idea of changing application and having many VIs open to see if that could cause the crash.

    //Mike

  2. I only add the important inputs and outputs to methods when they help me/others understand the design, but most often I leave them out of the class diagram.

    I use them more often in the sequence diagram.

    And regarding to: "You have to only use the 4x4x4 connector pane settings otherwise nobody can understand your code, and the world will go under", I just don’t get this.

    I’ve always used 6x8x6, for all my classes and I love it :D

  3. Foo(in MyClass_in:MyClass, out MyClass_out:MyClass)
     

     

    This looks nice, but should you really need to specify that the class method should have a class in/out value?

    I don't see you adding the Error-In/Out data to all methods  ;)

     

    If you like to have code generation from the UML, I guess it does make sense to add the class in/out value since the method could be static.

    But maybe it's better to always assume you're having the class in/out unless you wire.

    <<static>> MethodName (...)

    And maybe even:

    <<static>><<Error Less>>  MethodName (...)<<static>><<Non Virtual>> MethodName (...)<<static>><<Non Dynamic Dispatch>> MethodName (...)

    Cheers,

    Mike

  4. 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  

    • Like 1
  5. Hi

     

    I have tried to make a small UML diagram in the Symbio GDS, but it fails to generate the whole code. It only make a part of it and then turn into an error. I have sent the Error code but haven't got an answer yet:-(

    Am I doing something wrong? Se attached pictures.

     

    Hope for help;-)

     

    Edit: I use LV2013 and GOOP GDS4.6

     

    Regards Bjarne

     

    attachicon.gifUML symbio.PNG

    attachicon.gifGenerated code.PNG

    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

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.