Book a Demo

Author Topic: The package content doesn't modifiable  (Read 6982 times)

Gabor

  • EA User
  • **
  • Posts: 37
  • Karma: +0/-0
    • View Profile
The package content doesn't modifiable
« on: November 25, 2005, 05:04:24 am »
Hi,

I put a package, containing UseCases on the UseCase diagram, that set to show the package content.

After modifying the package, the content doesn't change on the diagram.

If I create a new package, and move the content of the beformentioned items to the new package, on seems empty on the diagram.

I found the workaround: export and reimport the package.

Thanks,

Gabor
« Last Edit: November 25, 2005, 02:20:54 pm by Gabor »

Hans

  • EA User
  • **
  • Posts: 78
  • Karma: +0/-0
    • View Profile
Re: The package content doesn't modifiable
« Reply #1 on: December 04, 2005, 06:57:38 am »
Great suggestion, Roman: package diagrams must reflect changes.

Greetings
Hans

thomaskilian

  • Guest
Re: The package content doesn't modifiable
« Reply #2 on: December 06, 2005, 01:17:16 pm »
Sounds more like bug, doesn't it?

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: The package content doesn't modifiable
« Reply #3 on: December 06, 2005, 02:25:45 pm »
While we're on this ... I wish ...

If ShowPackageContents is set in the diagram properties, could we have an option to just show the first level of package contents.  Since I use composite elements as h*ll of a lot, I get extremely looooong packages showing the elemets from all levels of the decomposition.  This hides the "significant information"  :( that could be gotten from just seeing the first level elements there.

bruce
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: The package content doesn't modifiable
« Reply #4 on: December 06, 2005, 02:39:33 pm »
Quote
While we're on this ... I wish ...

If ShowPackageContents is set in the diagram properties, could we have an option to just show the first level of package contents.  Since I use composite elements as h*ll of a lot, I get extremely looooong packages showing the elemets from all levels of the decomposition.  This hides the "significant information"  :( that could be gotten from just seeing the first level elements there.

bruce
Seconded...

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Aaron B

  • EA Administrator
  • EA User
  • *****
  • Posts: 941
  • Karma: +18/-0
    • View Profile
Re: The package content doesn't modifiable
« Reply #5 on: December 06, 2005, 03:04:21 pm »
Bruce, Paolo,
As of EA 6.0 (possibly around build 778, but not certain off the top of my head), the package contents behaviour should have changed so as to only display the first level child elements.  Sub-Elements should no longer be visible in the package contents.

There was a bug relating to elements not appearing in the package contents when the element had been moved from it's original location.  This should be fixed in build 780, which should be available soon.

If there are any problems with packages not refreshing their contents, please give precise details of how to reproduce.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: The package content doesn't modifiable
« Reply #6 on: December 06, 2005, 07:28:43 pm »
Aaron, you got there before I got a chance.

I can confirm though that it was from the first beta of 6.0 that the inner elements stopped being displayed.

AshK

  • EA User
  • **
  • Posts: 137
  • Karma: +0/-0
    • View Profile
Re: The package content doesn't modifiable
« Reply #7 on: December 06, 2005, 08:03:30 pm »
Quote
After modifying the package, the content doesn't change on the diagram.


Hi Gabor,

I can confirm that this is a bug.

Please find that it has been corrected in our next release, 780.

Thanks,

Ash
« Last Edit: December 06, 2005, 08:04:54 pm by AshK »
The Sparx Team
[email protected]