Book a Demo

Author Topic: Dockable Element - what does it actually mean?  (Read 4621 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Dockable Element - what does it actually mean?
« on: September 03, 2009, 03:19:49 pm »
I set the <context menu>|Dockable checkbox but the partition still behaves as though it's not set.  The same with some activities (in Rectangular notation).

There doesn't seem to be any indication that the element is "docked".  I would have expected that if the element was docked the option would change to <context menu>|Undock.

I expected that if two elements are "docked" and I move the "common" boundary, the other element will change it's shape appropriately.

Also, while docked the set of docked elements would behave as a "group".

Have I misunderstood how the Dockable menu item (should) works?

TIA,
Paolo
« Last Edit: September 03, 2009, 03:20:08 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Dockable Element - what does it actually mean?
« Reply #1 on: September 03, 2009, 06:13:01 pm »
From what I see it is far less then you expect.
It just makes object "snap" together when positioned close to each other. Nothing more, nothing less.

Geert

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Dockable Element - what does it actually mean?
« Reply #2 on: September 03, 2009, 06:16:15 pm »
Quote
From what I see it is far less then you expect.
It just makes object "snap" together when positioned close to each other. Nothing more, nothing less.

Geert
How close do they have to be to "snap"?  I'm not even seeing that (I think).  Although I'm quite ancient, I still have 20/20 vision.

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

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Dockable Element - what does it actually mean?
« Reply #3 on: September 03, 2009, 06:30:31 pm »
very close, but you should see that the corners line up nicely if you place two dockable elements together.

Geert

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Dockable Element - what does it actually mean?
« Reply #4 on: September 03, 2009, 06:41:06 pm »
Quote
very close, but you should see that the corners line up nicely if you place two dockable elements together.

Geert
Thanks, Geert!

Got it now...

Quite underwhelming...

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

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Dockable Element - what does it actually mean?
« Reply #5 on: September 09, 2009, 01:15:29 pm »
Although the Help documentation implies that the dockable attribute is owned by an Element, it appears to be owned by the DiagramObject.  

That is, an element can be dockable in one diagram and not in another.  Having set the property in one diagram I refreshed all diagrams in which the element appears and only the "dockable" diagram had the property set.

Can anyone (especially a Sparxian) confirm that this is the designed behaviour and the documentation needs to be updated?  Or not, as the case may be.

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

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Dockable Element - what does it actually mean?
« Reply #6 on: September 09, 2009, 05:18:56 pm »
It seems logical that the "dockable" property is related to the diagramobject rather then the object itself since this option only influences how the object reacts on a diagram.

But of course the help documentation should reflect that then.

Geert

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Dockable Element - what does it actually mean?
« Reply #7 on: September 09, 2009, 05:20:17 pm »
Quote
It seems logical that the "dockable" property is related to the diagramobject rather then the object itself since this option only influences how the object reacts on a diagram.

But of course the help documentation should reflect that then.

Geert
I agree, but what woudl I know?

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