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.


Topics - qwerty

Pages: 1 ... 10 11 [12]
166
When defining a connector in a toolbox it is possible to choose the type. But how can I specify the direction? I want to define an undirected association but the connector is always created Source->Target since there is no way to set this default.

(I tried setting the notes to direction="undirected" and direction="Unspecified" but that does not work.)

Help!

q.

167
Automation Interface, Add-Ins and Tools / OnPostNewConnector
« on: March 31, 2012, 04:12:22 am »
Probably one more of those bugs where only a few get bitten. When I change the name during OnPostNewConnector this is reflected as expected. But as soon as I try to change the Stereotype or the Type EA simply ignores any change.

Will not send a bug report as I need a work around now.

OT: I used to program a completely different product. Not too long after starting I found that programming meant "find a way around the mines in the field" (aka API-bugs). EA is similar.

q.

168
EA exports linked documents as base64 encoded zip. So far so good. But each time I export such a linked document the encoding is different although nothing has changed. Why? Does anybody know?

q.

169
Automation Interface, Add-Ins and Tools / Repository.Execute question
« on: April 28, 2011, 11:40:45 pm »
Does anybody know a way to pass parameters? I tried
Code: [Select]
Repositotry.Execeute ("INSERT INTO table ('col1', 'col2') VALUES (?, ?)", val1, val2)but that did not work. Especially I want to insert a BLOB (image) which is probably not so nice using quoted values.

q.

[edit:] I found a way to insert a BLOB by using 0x notation for the binary data (which is a workaround as this differs between databases).

[argh!] Now I get DAO.Database errors when trying to insert the BLOB. Jet 3 and 4 messages are different but none of them works. Bah! Mikeysoft!

[edit:] It now seems to be obvious that there is a 64k limit to the SQL string length. Who can be blamed for that? (I guess you need to tell Mikeysoft that BLOBs and the according SQLs are large - I have a faint remembering...) However, I'll report this as a bug to Sparx.

170
Automation Interface, Add-Ins and Tools / Annoying API change
« on: April 06, 2011, 01:31:57 am »
I was able to get around this up to now, but this is really annoying: The Elements method has changed behavior from 7.5 to (I guess it was already 8.0 but I'm testing with) 9.0. Package.Elements returned ALL elements of a package even those nested inside other elements. Definitely this behavior was wrong and needed correction. But simply changing the method's behavior is definitely the wrong way! As long as there is no way of versioning interfaces the new behavior should have been wrapped in another method named for example ElementsOnTop (or whatever). What I have to do now it to code something like
Code: [Select]
if rep.EAEdition < 4711
  use Elements the old way
else
  use Elements the new way
end
That sucks definitely.

Please, Sparxians: the next time you change an interface make it either during a beta testing phase for a new interface or introduce a new method for any changed behavior.

q.

171
Automation Interface, Add-Ins and Tools / REFGuid and Shape Script
« on: February 04, 2011, 11:08:31 pm »
I have massive problems using REFGuid tags together with shape scripts. My shape script issues a
Code: [Select]
if (HasTag ("BT::Block::Deployment")) {
      print("[");
      print("#TAG:BT::Block::Deployment#");
      print("]");
}
(I tried with and without qualifying the tag.) Now some models using the profile show the tag as intended. Others do not show anything at all (only after temporarily changing the tag value). Again other models do show the GUID instead of the elements name. I can't see any coherent picture. EA seems to behave randomly. Anyone else experiencing similar issues?

q.

172
I wonder if anyone else has encountered this: When I create an element from my MDG toolbox (a stereotyped Use Case) the OnPostNewElement event is fired AFTER the properties dialog has been closed. In contrast when I create a simple Use Case (from UML) the event is fired prior to opening the properties dialogue.

I'll report a bug any way.

q.

173
Automation Interface, Add-Ins and Tools / Tagged Values in MDG
« on: January 25, 2011, 04:36:19 am »
I have a problem with Tagged Values in MDG files. My MDG includes a number of Tagged Values which I expect to be present in the models using the MDG file. In the MDG wizard I select those tags (various: Memo, REFguid; DateTime; Enum). The resulting MDG does contain the values in a own section. However, my models using the MDG do not show any of the selected Tagged Values. Am I doing something wrong or does that no not work?

q.

174
Automation Interface, Add-Ins and Tools / Change diagram type (icon)
« on: December 22, 2010, 08:39:54 pm »
Hi all,
according to the documentation the Type attribute for a Diagram is read only. When creating a diagram it is possible to set the type in the AddNew with the second parameter (e.g. AddNew ("Diagram name", "Custom") to get the red lined directory like icon). Further it is possible to set the StyleEx of the diagram which will change the value shown at Diagram/Change Type from the context. But unlike this context menu the StyleEx will not change the Type accordingly!

So either StyleEx must change the icon (and Type) accordingly or Type must be read/write.

This is a bug, isn't it?

q

[edit] It appears that StyleEx silently ignores changes. "Reserved for Sparx Systems" according to docu. Nicely. Why do they publish their private interface? To confuse the users, I guess.

So in the end there are just two way: croak "Please change it manually" or to create a new diagram with cloned contents and delete the one in question. Any other solution?

175
Hi there,
does anybody know how to get the diagram from a UMLDiagram element (created via dragging a diagram onto another as Diagram Reference)?

I guess it's somewhere in the obscure XREFs since none of the primary UMLDiagram attributes seem to link to the originating diagram itself.

q

[edit] Actually it appears to be in PDATA1

Pages: 1 ... 10 11 [12]