Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - KP

Pages: 1 ... 150 151 [152] 153 154 ... 165
You can intercept the double-click event and open your own properties dialog. Search the help for EA_OnContextItemDoubleClicked

how do these orphans appear and is there any way to delete them?
As Paolo mentioned, an orphan is an element that doesn't appear in any diagram. This is perfectly valid. In fact it's perfectly valid to have a model without any diagrams at all in which case all elements will be orphans. So by all means delete them if they need deleting, but not just because they're orphans.

Automation Interface, Add-Ins and Tools / Re: Model Searches
« on: March 15, 2010, 08:53:46 am »
Try ea_guid...

Code: [Select]
SELECT Supplier, ea_guid as CLASSGUID FROM t_xref WHERE t_xref.Name='Element' AND t_xref.Type='reference' AND t_xref.Client='<Search Term>'

Automation Interface, Add-Ins and Tools / Re: Profiles and diagrams
« on: March 09, 2010, 01:10:49 pm »
You can do it but it's quite involved. You will need to define a custom toolbox - look up Toolbox Profiles in the help file. Then you will need to define a custom diagram type - look up Diagram Profiles in the help. One of the attributes for a custom diagram type is the toolbox to be opened whenever the diagram is opened. You will then need to bundle your toolbox profile, diagram profile and your original profile into a single MDG Technology (Tools>Generate MDG Technology File to launch the wizard). Settings>MDG Technologies>Advanced>Add to point to your technology then restart EA. Begin browsing the help on this page and ask questions if you get stuck!

Automation Interface, Add-Ins and Tools / Re: Tagged Value Multiplicity
« on: February 26, 2010, 11:54:13 am »
Yes, that's the same point that Van made higher up this thread.

At the moment, the only way to constrain the creation of an «eats» dependency so that the client must be a «predator» class and the supplier must be a «prey» class is to write an add-in. [If you decided to do this, you would need to implement the EA_OnPreNewConnector broadcast handler and return false if the constraints weren't met - see help for details].

A possibly simpler way, which doesn't force the user to make the correct connection but only encourages them, is to define quicklinks [again, see help for details]. If your quicklink definitions provide an eats dependency between prey and predator and nothing else, then it's easier for the user to do the right thing than the wrong thing. You can back this method up with a model validation script or add-in.

Well it's almost Friday lunchtime, so: KP ---«eats»--->"Chicken Parma"  8)

Automation Interface, Add-Ins and Tools / Re: Tagged Value Multiplicity
« on: February 26, 2010, 11:05:00 am »
How does one specify a RefGUIDList on a taggedValue association in a UML Profile? I know how to specify it in the UML Tagged Value Types, but I'd like to duplicate the function in my profile.
I don't think you can do it with the taggedValue association. Instead, give the «stereotype» class an attribute with the same name as the RefGUIDList tagged value type that you have defined.

Automation Interface, Add-Ins and Tools / Re: Tagged Value Multiplicity
« on: February 26, 2010, 11:00:56 am »
What do you mean by "stereotyped dependency", and how do I do this?
Consider classes named Lion, Antelope and Gnu where Lion has a RefGUIDList tagged value named "eats" which references Antelope and Gnu. An alternative way to model the same thing is to create a dependency relationship from Lion to Antelope and give the dependency the stereotype «eats». Do the same from Lion to Gnu. The stereotype can be any name that has meaning to you, but mustn't be a UML keyword.

Automation Interface, Add-Ins and Tools / Re: Tagged Value Multiplicity
« on: February 24, 2010, 10:48:57 am »
RefGUIDList tagged values should be what you're looking for. If you can't get them to work, please send in a support request - somebody in Support ought to be able to help get you up and running.

However, I wouldn't actually use tagged values to model one:many or many:many relationships - I think creating something like a stereotyped dependency between the elements is much simpler.

Ah sorry, I looked up the wrong event. No, EA_OnPostNewDiagram is new for EA 8.0...

EA_OnPostNewDiagramObject was added at version 7.1.833

I just realized that the EA_OnPostNewDiagramm event doesn't occur after a Diagram has been created, but an object within a diagram, so I am now without a clue how to add standard elements to a diagram on it's creation.
That sounds like you are using EA_OnPostNewDiagramObject. EA_OnPostNewDiagram should do exactly what you want it to do. This is what the help claims:
EA_OnPostNewDiagram notifies Add-Ins that a new diagram has been created. It enables Add-Ins to modify the diagram upon creation.
If that isn't happening then please send in a bug report with a code sample. Thanks.

Look for parentedge in the help file.  It doesn't say what the possible values are, but you can work it out fairly quickly by printing it and then moving a port around.
"Right", "Left", "Top" and "Bottom"

No, the ID isn't unique across all types.

Repository.CustomCommand("Repository", "SynchProfile", "Profile=MyProfile;Stereotype=MyStereotype;")

Pages: 1 ... 150 151 [152] 153 154 ... 165