Hiding Diagram Objects on a diagram

[KP]

The properties I am talking about belong to Element Stereotypes (please see the bottom of the page below).
These are properties that can have different values on different diagrams for the SAME element.

Therefore, I am assuming that they belong somewhere to the DiagramObject class but can't find where to access them.

They are in t_diagram.StyleEx, look for "OPTIONS_"

[Jayson]

Hey KP

I'm assuming I access this via the Diagram.StyleEx property?
If so, I did that and couldn't find anything.

Given that the properties I am talking about seem to be attached to the Diagram Objects (and not the Diagram itself), would it make sense for them to be in the diagram database table?

Cheers :-)

[KP]

I'm assuming I access this via the Diagram.StyleEx property?
If so, I did that and couldn't find anything.

It looks like they are only saved in that field when they are different to the default.

I checked this the following way: Start with an empty model, Perspective->Construction->Project Management, new diagram, put two "Sprint" elements on diagram, select one of them and right-click->Show as Requirement.

[Jayson]

Hey KP

But I am trying to access properties attached to specific diagram objects and NOT the diagram itself, so shouldn't the data be somewhere in the t_diagramobject table???

I am really confused! :-(

Jays :-)

[KP]

Each diagram object has a DUID (like a GUID but only 8 characters; stored in the t_diagramobjects.ObjectStyle field) and that DUID is referenced in the t_diagram.StyleEx field. e.g. "OPTIONS_3FA0FE61=DrawAsRequirement=0;"

But I am trying to access properties attached to specific diagram objects and NOT the diagram itself, so shouldn't the data be somewhere in the t_diagramobject table???

I'm sorry, I have no insight into why it was done this way.

[Jayson]

Thanks so much KP! :-)

Now that I know where the flags are stored, its pretty easy to hack the fields to get the outcome I am after.
Honestly I don't think I would have ever found the flags on my own, they are NOT in a remotely intuitive place are they?

Cheers

Jays :-)

[Geert Bellekens]

The "trick" to finding stuff like that is to use a profiler (such as on SQL Server) that captures all SQL statements issued to the database.

Start the profiler, change whatever you are interested in, stop the profiler, and examine the SQL update/insert/delete statements

Geert