MikaelH

I've added the Rename function in the latest OpenGDS version.

It's currently building and will be uploaded soon.

I've not added this feature in GDS yet, but why not, give me a day or so :-)

 (LabVIEW is not really good at OO).

I don't agree  , LabVIEW's OO is almost perfect, if we just had native interface, it would be perfect.

When I like to run things in different thread, and don’t like to make a fixed amount of while loops on my diagram. I use Active Objects.

I’ve created a demo application that does exactly what your Java Code is doing.

To be able to do this quick I use GDS which will make 80% of the code for me.

Cheers,

Mike

Threads.zip

It don't crash my 2014-32bit

You can easily do this yourself by modifying the class templates located in this folder:

LabVIEW 20XX\resource\Framework\Providers\XXXXXXXXX\ClassProviders\Provider_EndevoGOOP400\Templates

In the latest release on OpenGDS, I have fixed this in the utility VI:

LabVIEW 20XX\vi.lib\addons\GOOPUtility\GOOPUtil_IsValidReference.vi

Excellent work, thanks.

Absolutely, but if you want to make it a Generic VI, it’s a bit harder.

But if you don’t mind adding a VI like that in all your classes, that would be the easiest way.

You can always check out NI's GDS.

Look in VI:

C:\Program Files (x86)\National Instruments\LabVIEW 20xx\resource\Framework\Providers\Symbio_GDS\ClassProviders\Provider_LvNativeClass\ClassWriterNative_class\CreateMethod.vi

Thanks Mark.

We count on you as always.

I don't know anything about the internals of LabVIEW window management, so I can't speak to whether or not what you're seeing is intended behavior when the windows are reparented via winapi calls.

 

Here's a VI that may help, though. This password-protected VI (saved in LabVIEW 2013) calls a private VI Server property to suppress LabVIEW editor dialogs. Call this VI before you do your scripting, with a TRUE input. Then when your scripting is done, call it again with a FALSE input to reenable LabVIEW editor dialogs. <standard disclaimer here about using private LabVIEW functionality in production code>

 

Suppress Dialogs.vi

Darren, can you make a 2012 version f this?

If I can't solve it easy, I just create a small Autoit(www.autoitscript.com) application, that always runs and closes any unwanted dialog boxes.

Re: Design Patterns

Hi Mikael,

 

When I run the remoteloader.vi in the CommandPattern project I get the error 1100:

 

Obtain Queue in RemoteControl.lvclass:GuiRepository.vi->RemoteControl.lvclass:ControlGuiWindow. vi->RemoteLoader.vi

 

I am wondering if this error has anything to do with the labview version I am using (2013).

 

thanks

 

Helcio

Sorry I just saw that I use my own dialog VI, in the Door,Fan and Light classes.

Replace the VI: LcDialog_AutoSizeDialog.vi, with a single One utton Dialog.

The VIs you need to update are:

GarageDoor_classOpen.vi  Close.vi

Light_classOn.vi Off.vi

CeilingFan_classSetSpeed.vi

Missing class

...but don't try this, it crashes my LabVIEW (2012P1f5)

I'm working on it, you can try this solution, it looks likes it works in 2012 at least.

But I'm not sure if it should work, we better ask NI.

Make sure you convert the number string to U32, not I32 that is the default

Cheers,

Mike

If you are new to OO, NI's GOOP Development tool, will make life easier fot you, BTW it's free.

Check out the videos at the community page to see if this tool is for you.

https://decibel.ni.com/content/message/44088#44088

You'll call them in parallel like God and dataflow intended.

Awesome.

Hi Mikael,

 

I am trying to build the abstract factory pattern with GOOP and I do not know how to check if an object reference is not empty in Labview.

In JAVA this was done like this:

 

How can I do this in labview?

What class type are you using?

If it's a GOOP3 type, you can use the Utility VIs (under Addons->GOOP Utility) GOOPUtil_IsValidReference.vi

NI is uploading projects to GitHUB, so the LV community can help out in development.

The GOOP Development Suite will be one of the first projects they will try out.

I hope many of you will help NI, to make this product better.

http://vishots.com/category/live/

http://youtu.be/abXD7M7-Y1Q

Try this

Data.vi

Try this:

ModifyImage.vi

Cheers,

Mike

TortoiseXXX is great, but which one should I use today :-)

I've noticed this in later version of LabVIEW, and never has the problem before.

The same application, just converted to LV2012SP1 for example.

# http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/lv_file_extensions/*.aliases*.lvlps

How can this be improved?

Perfect, but why can't NI put these files somewhere else ;-)