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 - qwerty

Pages: 1 ... 598 599 [600] 601 602 ... 630
8986
Geert posted a solution a short time ago. Either good luck with the search or Geert will be faster.

q.

8987
Automation Interface, Add-Ins and Tools / Re: UML Profiles
« on: December 20, 2012, 09:11:23 am »
Haven't developed that, you need to ask Sparx...

q.

8988
Automation Interface, Add-Ins and Tools / Re: UML Profiles
« on: December 19, 2012, 08:14:52 pm »
You can not really limit them. The quick linker just presents the useful subset of connectors. But via the standard toolboxes one can create any UML-valid connector. If you really want to do a check you need to intercept the creation via the OnPreNewConnector event.

q.

8989
Automation Interface, Add-Ins and Tools / Re: statechart
« on: December 19, 2012, 10:15:38 pm »
Undocumented and unsupported but valid as parachute:  
Code: [Select]
Repository.Execute('INSERT INTO t_xref ....')To create the XRefID use any algorithm to create a GUID (there's something inside the Windoze libs or your language specific libs).

q.

8990
Automation Interface, Add-Ins and Tools / Re: Apply Stereotype
« on: December 07, 2012, 04:30:59 am »
I guess you have to upgrade. It's (almost) impossible to create the tagged values for a certain MDG. I explained that in my Inside EA book pg. 35:
Quote
As mentioned above there’s some magic with GUIDs for tagged values that come from a MDG profile. These look exactly like ‘normal’ GUIDS:
{aaaaaaaa-aaaa-aaaa-bbbb-bbbbbbbbbbbb}
Here the a and b hex codes are not completely random. Only the b part is completely random, but the a part is a hash code computed individually per profile. The hash algorithm is internal to EA and unfortunately not known.

q.

8991
Diagram.SelectedObjects

q.

8992
Automation Interface, Add-Ins and Tools / Re: API: Diagram
« on: November 26, 2012, 09:32:55 pm »
PDATA1 == 0 -> text
PDATA1 > 0 -> Hyperlink

q.

8993
Automation Interface, Add-Ins and Tools / Re: API: Diagram
« on: November 26, 2012, 07:33:27 am »
PDATA == MISCDATA; but there's no equivalent for NType

q.

8994
Automation Interface, Add-Ins and Tools / Re: API: Diagram
« on: November 26, 2012, 12:02:29 am »
See my book page 7: PDATA1:For UMLDiagrams: Diagram_ID of the underlying diagram;
here NType == 0 means Frame and 1 Reference


q.

8995
Wasn't there a recent  post from KP where he told how to do that?

q.

8996
Quote
It's in the connector's StyleEx field. It might contain something like "LFEP=<TargetGUID>R;LFSP=<SourceGUID>L;". Use the GUIDs to look up the linked features in either the attributes table or the operations table.
I should have read my own book  (page 40) :-X

q.

8997
I'd guess this information is deep in EA's guts. Likely it's in the table t_xref. I can't remember having searched for this yet.

q.

[edit] No. It's in the Note's PDATA. PDATA1="ElementNote" (or whatever you used); PDATA2=element-id of object. Its more complicated for linked attributes. For that I did not find the referring element-id.

8998
Sorry Markus, but my java knowledge is very little. To me the code looks okay. I'd try to put more trace into it. E.g.: Name the connectors of the package in EA and print the names of the connectors. Somethig like
Code: [Select]
System.out.println("Conn name: "+conn.GetName());
So you see you have the right connectors at all.

q.

8999
Each connector has the object id of the connected elements (ClientID and SupplierID). Use these to get according elements via Repository.GetElementByID. There you can retrieve the Attributes collections.

Further I'd recommend my book Scripting EA.

q.

9000
Ask in a forum about the language you are using.

q.

Pages: 1 ... 598 599 [600] 601 602 ... 630