New elements from profile toolbox: in which package should they be created?

[Frank Horn]

Build 828: when I drag an element from a standard toolbox onto a diagram, the element is created in the diagram's parent package.

An element from one of my own toolboxes (from an MDG file loaded the 7.1. way) is created in the package selected in the project browser, no matter where the diagram belongs onto which the element has been dragged. This even happens when the package selected in the project browser is under version control and locked.

Is this supposed to be new feature?

[«Midnight»]

I strongly doubt it Frank.

In particular, creating a new element in a locked package is definitely not something that should be happening, at least not without some pretty convincing documentation.

My suggest is that you try this under build 829, or at least check the release notes for anything relevant. If the problem seems to persist, make an immediate bug report to Sparx.

David

[Frank Horn]

Still the same with build 829.

Filed a bug report:

Subject:

Elements from profile toolbox created in wrong package

Details:

When I drag an element from a standard toolbox onto a diagram, the element is created in the diagram's parent package.

An element from one of my own toolboxes (from an MDG file loaded the 7.1. way) is created in the package selected in the project browser, no matter where the diagram belongs onto which the element has been dragged. This even happens when the package selected in the project browser is under version control and locked.

Of course the element can not be dragged out of the locked package. The damage can only be undone by deleting it from the diagram and then performing GetLatest on the locked package (enforcing reload from XML cause EA thinks the package is up to date).

Steps to reproduce:

Create an MDG technology including diagram and toolbox profiles.
Copy it to the MDG technologies subfolder of the EA program folder.
Start EA, and create a new eap file with two packages.
Put one package under version control (SVN).
Make your technology the active one and create a diagram of a type defined therein in the unlocked package.
Select the locked package in the project browser.
Drag an element from the toolbox to the diagram.

[brannstrom]

I have had users reporting that existing elements move around between different packages when they are working with diagrams. And the packages are locked with versioncontrol. This is very strange and I don't know when it happens and what causes it. Perhaps this is a related issue. They are using EA 6.5.

/N

[«Midnight»]

I have had users reporting that existing elements move around between different packages when they are working with diagrams. And the packages are locked with versioncontrol. This is very strange and I don't know when it happens and what causes it. Perhaps this is a related issue. They are using EA 6.5.

/N

Is there any way you can send to Sparx a compressed project that demonstrates the problem? If so, use the bug report page, and include everything you can think of relating to your VC product and configuration.

Regardless of whether this relates to Frank's problem, this is definitely something that needs to be resolved. [Or if it has already been solved in 7.1, it needs to be documented. It might be mentioned in the release notes, but is likely one of those things you won't recognize easily.]

David

[brannstrom]

I have had users reporting that existing elements move around between different packages when they are working with diagrams. And the packages are locked with versioncontrol. This is very strange and I don't know when it happens and what causes it. Perhaps this is a related issue. They are using EA 6.5.

/N

Is there any way you can send to Sparx a compressed project that demonstrates the problem? If so, use the bug report page, and include everything you can think of relating to your VC product and configuration.

Regardless of whether this relates to Frank's problem, this is definitely something that needs to be resolved. [Or if it has already been solved in 7.1, it needs to be documented. It might be mentioned in the release notes, but is likely one of those things you won't recognize easily.]

David

Sorry to say I can't send in the project. Since I don't know when or how i happens I can't make a sample project with the problem. Right now I just got an indication that this can happen. I hope to get more clues in the future.

/N