Generic Table / Value Property Tables (useability)

[daniel.treachler@orbitalatk.com]

One thing that would be very useful is a better way to manage value properties that are owned by structural elements.

Consider a scenario where you are trying to reuse component definitions in a library:

image1.PNG

It would really be nice to be able to make a list of components, and values of the owned properties as columns within the table. This is currently possible (although very clunky) with generic tables & metachain navigations, see below:

image2.PNG

(the associated metachain:)

image3.PNG

Use Metachain: block-> owned element
Use filter: filter owned elements based on name
Use Metachain: property->default value

The problem is that:
A) making all the metachains is time consuming, and not particular user friendly
B) all of those columns become read-only, making changes much more labor intensive.

I realize this type thing can be done using instances & instance tables; but I would be very useful to be able to do this at the block / specification level. Perhaps there is already a way to make the columns read/write, would love to hear it.

[osvaldas.jankauskas@nomagic.com]

Hello,

Thank you for your questions.

According to your need, we can suggest you set Value Property as element type of Generic Table. By doing this, you can insert default values directly from the table. Also, you don't need to build complex expressions for achieving this. See table below:

Value Property tables.jpg

In addition, the value properties can be grouped by owner.

If you have any other questions or concerns - feel free to contact us.

Best regards,
No Magic, Inc. Customer Support