Jump to content

burd

Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by burd

  1. Hi Mikael, I am trying to do the second solution indicated in the picture Interface2.png: The reference for the Duck class is invalid when the method PerformFly is executed, then I get the error 1556. How do I do this the right way? Thanks Helcio Duck2.zip
  2. Hello Mikael, I tried to use the interface the way you described, but I am getting an error (invalid reference) and I cannot figure out how to fix this. Could you give me a help with that? thanks Helcio GOOP DUCK.zip
  3. Hi Michael! It is great that you can still help the community. thank you
  4. Hello Michael, Are you going to continue supporting GOOP now that NI bought it? Are you still answering questions? thanks Helcio
  5. There was some minor modifications to the VIP files, and here follow it attached: Goop Timer 3.vip
  6. Hello Mikael, I have modified the example as you suggested: and also created 2 extended classes to observe how the Create Class Method behaves for an extended object: And in example 3 are the extended classes at work: follow attached the files: hb_lib_goop_timer-1.0.0.4.vip Please, let me know if those procedures are fine, thanks again for your help! Helcio
  7. Hello Mikael, I redone the timer based on the advices you gave me: Everything is now by ref, and the class atributes design pattern was apllied. Now the attribute is updated when the opject is created like this: Now it works,and the class attributes design pattern woks like magic. Now I have similar functionality to static variables in java (I think). If you can check and see if everything is really fine would be nice. Follow attached the package with the vis. Timer GOOP 2.vip Thank you for the help! Helcio
  8. Hello Mikael, I am sending the timer goop.vip file attached. In this example there is a class called timer created with the GDS, I do not know why the attribute "Number of Timers in Memory" is not being updated the way I think it should work. I would expect that when the class is created, this attribute is updated and somehow kept in memory, so that another object of the same class type can access and modify it. In the example sent, why the attribute Number of timers in memory (in the Example 1.vi and Example 2.vi ) are always resulting in 1? I would expect this value to be the total number of timer objects created, and in this case it is certainly more than 1. thanks Helcio Timer GOOP.vip
  9. Hi Mikael I believe that using the GOOP 4.5 Interface template I was able to build the strategy pattern. Please, give a look and let me know. The goop 4.5 provides a easy way to build an interface. I tried other methods before like the Interface Framework but I found it far too cumbersome. I am more confident to work with OOP in Labview because I know that at least I have the interface support from Endevo GOOP (Why does't NI provide interface support????). I can live without constructors, but without interface I don't think I can. thanks for the tips! Helcio Simuduck.zip
  10. Hi Michael, GOOP 4.5 is great, but due to my ignorance it is hard to take advantage of it. I am trying to use the UML to generate all the classes needed to create a strategy pattern. From the picture attached (LAVA does not allow me to attach the UML file) you can see what I am trying to do. However, when I generate the code, the interface does not seem to be created. There is no way to apply the Fly method in the FlyWithWings class to the MallardDuck class. Probably I am doing something wrong....could you give me a help with that? Thanks Helcio
  11. Hi Justin, I read your presentation. Unfortunately you may have forgoten to put the power supply presentation's example available for download. It is very hard to follow the example just by reading the power point presentation. Is there any chance you could put this example available for download? There is also another example in the power point presentation using LVx. Could you also make it available for download? Thanks Helcio
×
×
  • Create New...

Important Information

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