NXG (5.0) Self-documentation of a cluster - what a pain...

[billko]

In order for anything inside the cluster to have its own description it has to be a gtype (typedef).  How many bazillion controls am I going to end up with?

Example:

I just want a U8 with a description to say what it is.  I have to make that U8 a gtype.  One more file to save.  If I create a U8 on the cluster gtype, I can give it a description, but once I move it inside the cluster, that info is gone.  (As in, "gone forever".  If I take it back out of the cluster, the description is blank.)

I guess I can see the logic in that, though.  In my example above, once you define it as a gtype, that is what it is forever.  It will never lose its information.  It just means even bigger projects with even more typedef'd controls than I usually would have, which is "a whole bunch".  Come to think of it, maybe it's not so bad after all.  It forces you to use the same workflow for everything in the cluster.

Thoughts?

Thanks.

[billko]

I guess I was awrong about that, too.  I thought I was able to do this, but I guess not.  Even though gtypes retain their descriptions in the gtype, itself, it doesn't show up inside the cluster.  I guess the only is to assign a tooltip to each element.  But then it means it only shows up at runtime.  Not useful to a developer.