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 - Paolo F Cantoni

Pages: 1 ... 391 392 [393] 394 395 ... 410
5881
Yes, you will need to create a snapshot image of the diagram in order to preserve the soon-to-be-deleted element.

The diagram is a view into the model and therefore cannot show what is not there.

You will need to export the diagram as an image (Using Diagram|Save Diagram [Ctrl+T]) then re-import the saved image into the images set (using Settings|Images...)  Lastly you'll need to apply the imported image to an element (using <Element context menu>|Appearance...|Select Alternate Image... [Ctrl+Shift+W]).  If you want to be able to use the element in the browser - pick a suitable element type.  If you just want a shape to hold the image, you can use a boundary shape.

HTH,
Paolo

5882
Hi Martin,

IRC It CAN'T currently be done with the API.  We users have asked for it and there was some indication that Sparx would do it soon, but I don't think it ended up coming about.

I'm currently on a VERY SLOW connection - but I believe I (or someone else) posted the necessary direct DB operations to get "all the ducks in a row" and get it to work correctly.

Have a search in (probably) this category of the forum (I think less than a year ago) and see if it's there.  If not, let me know and I'll try to dig up the code later when I'm on a faster link.

HTH,
Paolo

5883
Automation Interface, Add-Ins and Tools / Re: OracleOleDB problem?
« on: April 20, 2010, 11:34:17 pm »
Quick look suggests a data typing problem...

try: select instr('Tag:Value',':') + '1' AS C1 from dual;

You should get '41' from both...

(Fingers crossed)  ;)

Isn't software wonderful?

HTH,
Paolo

5884
Quote
It appears to be used for filling listboxes and comboboxes, for example on the Auto Name Counters dialog (Settings > Auto Name Counters). You can also create a custom tagged value which enumerates the table contents (Type=Enum;List=ObjectTypes;)
Well one listbox it DOESN'T populate is the list of object types to change to...  :o

Paolo

5885
Can anyone tell me what the function of the t_objecttypes table is?

I've been running on an .EAP with an empty t_objecttypes table for a couple of hours and there doesn't seem to be any ill effects...  Maybe I've just been lucky?  The table has to exist - else EA won't start - but apart from that...

Paolo

5886
The EA Help shows how to define a default diagram type for a specific stereotype.

However, the _defaultDiagramType attribute is applied to the metatype, not the stereotype (don't really understand why, perhaps someone could enlighten me).

So how does one make different default diagram types where you have more than one stereotype extending the same metaclass?

Do you create more than one metaclass element (one for each diagram type)?

TIA,
Paolo

5887
Quote
The «metaclass» denotes a known UML metaclass.  To do what you want have a look at http://www.sparxsystems.com/uml_tool_guide/sdk_for_enterprise_architect/defining_a_stereotype_as_a_met.html
Hi Simon,

I was aware of the link but I believed it didn't actually do what I wanted.  I've just created my equivalent example and it confirms what I thought.  I've created stereotype "Term" which extends "Class" as per the example.

While it goes part of the way, it doesn't do what I need in one crucial area:
It creates a t_object of type Class with stereotype "Term".  I actually need to stereotype Term and so that would mean additional stereotypes - which (I think) I can't access in shape scripts.

What I'm after is a t_object of type "Term" - which EA could find by looking up the MDG - with NO stereotype.  Is that possible?

Sparx is able to create new types of objects - Requirements, Features, Changes etc.  It would be really cool if users could.  Initially, the default properties could be the generic classifier set.

Paolo

5888
When you create an MDG, you create profiles which start with «metaclass»(es) which get extended by stereotypes.

One of the available metaclasses is "Classifier".  I believe I understand what it is - it's the base item that "Class" and "Use Case" and "Activity" extend to define themselves  (please correct me if this is not so).

So, what is the function of this item in an MDG?   To allow us to create new types of metaclasses?  For example, I want to create a new type of thing - a Term.  I could extend "Class", but that would create a Class stereotyped «Term».  I'd actually like to create a new type of thing (such as a Requirement or Feature or Change etc).  This is because I want to stereotype Terms (with their own subset of stereotypes).

Can I use the Classifier metaclass for this purpose?  Should I be able to?  It would seem to me that the ability to for users to be able to create new types of elements (like Sparx is able to do would be REALLY REALLY cool...)

Thoughts?
Paolo

5889
Is it possible to stereotype a diagram within an MDG Technology?

I can create a new diagram type.  But I'd also like to set a stereotype.  Is it possible?

TIA,
Paolo

5890
Quote
In fact yes : it is possible to have a "generalize" link between a class and an operation, and even between 2 operations (you have to make a right click "link to element feature")
You have to be careful...  The linkage is (effectively) a rendering ONLY.  The t_connector details - as beginner says - ONLY refer to the end Elements (not Features).  It is NOT a simple matter to extract the rendering information and convert it to the (derived) Feature linkages.

HTH,
Paolo

5891
Quote
I've only ever used Element.Connectors, not Package.Connectors.
Has anybody ever used Package.Connectors?

Did it work?

Paolo

5892
Transformation records are kept in t_xref; Type="Transformation";  Name =<name of element>

HTH,
Paolo

5893
Automation Interface, Add-Ins and Tools / Re: Deployment Question
« on: March 24, 2010, 11:03:36 am »
Hi Tom,

Perhaps you could formally document your steps here - to save the rest of us some heartache...

TIA,
PAolo

5894
Quote
Actually, Element.Diagrams is the list of diagrams owned by the element.  Not the list of diagrams it appears on.
[size=18]...[/size].
And so it is!

That will teach me to try to answer questions at 3:57am in the morning!

Just because I can't sleep, it doesn't mean my brain is awake!

Apologies...

Paolo

5895
"Orphans" are elements that are represented in NO diagrams.

Therefore their Element.Diagrams collection should be empty.

HTH,
Paolo

Pages: 1 ... 391 392 [393] 394 395 ... 410