LabVIEW object default probe should show the content of Data typedef ...

[manu.NET]

Hello,

This idea exist certainly, but i don't find it ... so sorry if dupplicate ...

For the moment, the default probe for LabVIEW object is a string containing the "Class name" ... quiet poor !!! 

By default, the object probe should view the content of the object data type !

A Better idea would be, to view, in object probe, the content of the data type, using a Tree View Probe  ( also Dot Net Property browser, property grid ). 

Thanks a lot.

Manu.net.

[Intaris]

I like the "don't show if default" because then I only see what has changed, which is normally what I'm after when debugging....

[AristosQueue (NI)]

You are the first user I've heard who has said thank you for that feature. Most others I hear from want me to "fix" it.

[chris_d754]

I dislike the don't show if default :). This is because I use the Flatten to XML inconjunction with an INI initializer where I replace all the values based on the keys in the INI within the XML. In order to do this, I now have to initialize the object with some bogus value. This is especially frustrating when child classes are involved, as all levels of the object need now be initialized with bogus data.

[AristosQueue (NI)]

chris_d754: I'm not going to appologize for *not* adding a security hole into the object model.

Why not just have the objects read their keys directly from the INI file? Why do you have to populate an XML string and then unflatten that? It'd be more efficient to not go through that extra layer.

[chris_d754]

Not asking for an apology! Just saying how I like to use it. I do it this way so that I can change a class and not have to change any VIs. Its very efficient actually. I take the default class, change a parameter, flatten to XML, read the INI and manipulate the XML, then unflatten the XML, all with dynamic dispatch! It's great 🙂 And at no point do any VIs need to be touched, just add the data memeber and add a key to the INI and voila.

[AristosQueue (NI)]

chris_d754: Weirdly inspirational. I'll keep that methodology in mind when I'm looking further at the future of serialization.

[chris_d754]

Glad I could help in some small way! Let me know if you would like some example code.

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined.