Does "EndevoGOOP400" support GOOP Debugger?

[Tepig]

Hello GOOP community,

Im a new GOOPer, think the tool is really cool : D

I want to be a master of GOOP but have one question how can I do debugging.

According to this video, GOOP Suite provide a debugging tool.

It seems that EndevoGOOP300 supports but 400 doesn't. Is the behavior expected?

I read a help file but it said that

"This tool allows you to monitor the objects created from GOOP 3/4 and OpenG class templates."

My current project is below.300 was generated with Endevo300 template, 400 was with Endevo400.

And MAIN.vi

In MAIN.vi, create two objects. After the VI was executed, I saw the following result in debugging window.

I only can see an object of Endevo300 but couldn't see Endevo400. 

I want to use 400 version because it is the latest version (Isn't it?)

So if I can observe object behavior on Endevo400, it is really helpful.

Additional Information

LabVIEW 2017 (non SP1)

GOOP Suite (v1.1.87.94)

[JeffreyH · Accepted solution]

The GOOP400 classes are pretty lightweight in their basic form (which is a good thing!). So they do not contain debugging features by default. You can add the Debugging 'Design Pattern 'when creating the class:

or add it to existing classes:

[Tepig]

Hi Jeffrey, thanks for the comment!

I understand that GOOP400 is simpler than GOOP300, doesn't have debugging feature : )

Umm... Which version does everyone most use?

[JeffreyH]

I'd recommend to always use GOOP400 for new classes. It uses DVR and Inplace-element structure and is various benefits over GOOP300. GOOP300 is more there for legacy support.

I'd also recommend to use OpenGDS instead of the NI GOOP DevSuite. The NI one is the same, but a lot older and not regularly updated.

You can get it here: https://opengds.github.io/.

[Tepig]

Thank you for your suggestion! I will try OpenGDS : D

[Tepig]

Ummmm...!! Im really excited in OpenGDS!! There are many good updates.

Thanks JeffreyH : D

[MikaelH]

I'll recommend GOOP4 as well.