Topics

166

Bugs and Issues / Constraints deleted when package gets deleted

« on: July 30, 2009, 08:01:44 pm »

I've found a very disturbing bug.
When I add a constraint to a diagram, then move the diagram to another package, and then delete the original package the constraint is deleted as well.
Apparently the constraint is defined as a child element of the package, but it is not shown on in the project browser.
When the parent package of a constraint is deleted the constraint itself is deleted as well, and since I cannot see the constrain in the project browser there is no way to move the constraint to another package before deleting the original package.

Auch...

I've reported this to Sparx Support.

Geert

167

Bugs and Issues / InformationItem not in list Element/Change Type

« on: July 13, 2009, 09:12:26 pm »

The type "InformationItem" is not in the list that is shown when you select Element/Advanced/Change Type.
This leads to the strange situtation that I can change an InformationItem to a class, but this class cannot be changed back to an be an InformationItem.

Bug submitted to Sparx Support.

168

Bugs and Issues / Effect on Action does not wrap

« on: September 25, 2009, 10:29:37 pm »

When adding an Effect to an Action the textbox allows multiple lines.
When you check tick the checkbox "Show Effect in Diagram" the whole effect is displayed in one line stretching the Action to ridiculous propertions.
The effect on the diagram should be displayed in multiple lines just as in the tab of Action.

Reported to Sparx.

Geert

169

Bugs and Issues / Error when checking out package from TFS

« on: September 22, 2009, 05:21:16 pm »

Sometimes i get the error:
The current action cannot be completed as the necessary security is not available when checking out a package that is controlled in TFS.
Before it starts I get the dialog asking me to lock the package (as we have security setup with the option "Require user lock to edit"). I confirm that I want to lock the package, but sometimes it seems that there is a race condition where the checkout process begins before the locking is finished.
Trying again to check out a package works, but this is just annoying.
I've reported this to Sparx

Geert

170

Bugs and Issues / Multiselect broken in select<item> dialog

« on: September 08, 2009, 09:50:16 pm »

Hi,

I defined a tagged value that references a list of operations.
After adding my tagged value to an element I can select the operation with the select<item> dialog.
Multiselect works with Ctrl-select.
My problem now is that I cannot add an operation from another class/interface because opening a class/interface/package deselects wathever was selected and highlights the opened item.
According to the help file this should not happen:

Multiple Selection

Where an operation permits the selection of multiple items, the Select <Item> dialog is automatically enabled to support this. To select the items, press [Ctrl] as you click on each item. Having selected an item, you can continue to expand and browse the hierarchy, and/or search for items; the dialog retains the existing selections until you click on the OK button.

This is really annoying.

I'll report it to Sparx.

Geert

171

Bugs and Issues / New Note already filled in

« on: August 28, 2009, 10:52:51 pm »

When I add a new Note to a diagram it is already filled in.
It has a text and a non-standard color. (red)
Looks like there is some sort of default for new notes, but I don't seem to remember having an option to change the default for notes to include text.
This only happens on one model, for all users, so it is definitely something model based.
Anyone ever experienced the same? (or even better, knows the solution?)

Thanks

Geert

172

Bugs and Issues / Repository.GetElementSet("",0) results in SQL err

« on: July 31, 2009, 07:42:53 pm »

When I try to get all elements in my model using Repository.getElementSet("",0) I get an SQL server error: "The query processor ran out of internal resources... "
Our model is located on a  SQL server 2008 with 16GB of memory.
The t_object table contains about 45000 rows.
I guess the query used to retrieve these elements is not optimal and SQL server chokes on it.

173

Bugs and Issues / Error in documentation help (Method)

« on: August 21, 2009, 09:25:22 pm »

In the page about the Method (api reference)
it says

ParentID
 Long
 Read only. An optional ID of an element that 'owns' this diagram; e.g. a Sequence diagram owned by a Use Case.

This seems to be copy/pasted from the diagram documentation

Reported as bug.

Geert

174

Bugs and Issues / GetFormatFromField("RTF",text) add new p

« on: August 11, 2009, 09:25:12 pm »

The Repository.GetFormatFromField() with the parameter RTF is not working correctly.
I have two different strings to convert:

Code: [Select]

Repository.GetFormatFromField("\r\nStringWithNewLine\r\n");results in:

Code: [Select]

"{\\rtf1... (more RTF Codes)... \\saauto1 StringWithNewLine\\par}and

Code: [Select]

Repository.GetFormatFromField("\r\nStringWithoutNewLine");results in

Code: [Select]

"{\\rtf1... (more RTF Codes)... \\saauto1 StringWithoutNewLine\\par}It is this last "\\par" wich is wrongfully added in the GetFormatFromField function.
I will now have to find out first if my string has a newline and the end and if not remove the last "\\par" from the RTF string, pff... just the kind of thing I like   :-/

I'll report this as a bug.

Geert

175

Bugs and Issues / SQL error when element name > 255 characters

« on: April 28, 2009, 03:51:19 pm »

When you change the name of an object to be longer then 255 characters the GUI will allow it but you get an SQL error "string or binary data will be truncated" when it tries to save the element to the database. At first it seems like the name is accepted (the element shows the full name on the diagram) but when it is refreshed the name of the element is not saved to the database and reverts back to the original name (Action1)
The only seems to happen on a DBMS (SQL Server) and not on an Access repository. The latter will not show the error, but truncate the name anyway.

Steps to reproduce:

• Add a new action (or any other element) to a diagram
• In the name field paste a name longer then 255 characters
• Click OK
• Notice the error "string or binary data will be truncated"
• Notice that the full name (>255 ch) is displayed on the diagram
• Doubleclick the action on the diagram
• Click OK.
• Notice that the default name ("action1") is displayed.

In my opinion the GUI should validate the length of the name before trying to submit it to the database thus avoiding the technical error.
I'll report this to Sparx in a bug report.

Geert

176

Bugs and Issues / Issue.DateResolved cannot be set to null by api

« on: July 15, 2009, 10:22:06 pm »

When creating an issue through the automation interface
using following code:

Code: [Select]

EA.Issue defect = (EA.Issue)wrappedElement.Issues.AddNew("Defectname","Defect");
           wrappedElement.Update();
           defect.ElementID = parentElement.getID();
           defect.Update();the "DateResolved" field is filled in with 0:00:00
This has as effect that in the GUI the date resolved is filled in with "30/12/1899" and the checkbox is checked.
When adding a defect through the GUI the field is left null.
It is however not possible to set the field to null using the API.

I've reported this as a bug to Sparx

177

Bugs and Issues / InformationItem cannot be used parameter type

« on: April 10, 2009, 05:12:29 pm »

I was trying to use an information item as the type of a parameter and the return type of my operaration. The Application allows me to select the informationItem, but does not retain the information once selected.
Using an InformationItem as type should be allowed as in UML the information item inherits Classifier with inherits Type
The type of the Parameter is of type "Type" so informationItem should be allowed.
Steps to reproduce:
1. Create InformationItem (A)
2. Create operation
3. click on the "..." button to open the "Set Element Classifier" window
4. Select the just created InformationItem and click "OK"
5. Notice that the field "returntype is still empty
for the issue with the parameter type
1. Create InformationItem (A)
2. Create operation
3a. click on the "Edit Parameters" button
3. click on the "..." button to open the "Set Element Classifier" window
4. Select the just created InformationItem and click "OK"
5. notice that the field "Type" is empty

I've sent a bug report to Sparx as well.

178

Bugs and Issues / Unhandled COM exception at DiagramObject.Update

« on: May 14, 2009, 06:24:23 pm »

When I try to update my diagramObject afer changing its ElementID I get an Unhandled Com exception:

System.Runtime.InteropServices.COMException was unhandled
  Message=""
  Source=""
  ErrorCode=-2147221504
  StackTrace:
       at EA.IDualDiagramObject.Update()
  InnerException:

My litte C# program does following:
- Find all diagramObjects with a specific elementID
- Replace elementID with another elementID
- Update diagramObject.

It is in the update method that I get the unhandled COM exception. I'm testing this using EA v 7.5 b844 on an access backend.

As a workaround I'm going to try to create e new DiagramObject with the correct ID and the same settings, and then delete the old one.

179

Bugs and Issues / stereotype display error on collaborations

« on: April 21, 2009, 04:37:27 pm »

When resizing a collaboration with a long name the stereotype is being displayed multiple times.

Steps to reproduce:
- Create a collaboration with a very long name
- Add a stereotype to the collaboration
- Put the collaboration on a diagram
- Try to resize the collaboration by pulling the bottom up
- Notice that the stereotype is diplayed twice.
- Try resizing again and each time a new stereotype display is added.

If reported this to sparx as well.

180

Uml Process / BPMN 2.0: PartnerEntity or ParnerRole?

« on: October 28, 2015, 06:22:55 pm »

I'm trying to decide whether I need to use a PartnerEntity or a PartnerRole, so I naturally look at the BPMN 2.0 specs and try to figure out the differnence between the two.
That was kind of a disappointment. What I found was this:
- PartnerEntity: A PartnerEntity is one of the possible types of Participant (see the section above).
- PartnerRole: A PartnerRole is one of the possible types of Participant (see the section above).

So that didn't help all that much. The "section above" (could you be more specific please ) I assume refers to this part:

- partnerRoleRef: PartnerRole [0..*] The partnerRoleRef attribute identifies a PartnerRole that the Participant plays in the Collaboration. Both a PartnerRole and a PartnerEntity MAY be defined for the Participant. This attribute is derived from the participantRefs of PartnerRole.
- partnerEntityRef: PartnerEntity [0..*] The partnerEntityRef attribute identifies a PartnerEntity that the Participant plays in the Collaboration. Both a PartnerRole and a PartnerEntity MAY be defined for the Participant.This attribute is derived from the participantRefs of PartnerEntity.

Again, no definition of the difference between the two things.

Have I missed something, or is the specification of this language really this poor? :-/

Geert