Reinvent resizing of shapes with child or parent shapes (Pools+Lanes Problem)

[GoogleCodeExporter]

It turns out that the layouting of pools and lanes is not intuitive. This
comes from bad concept of how shapes influence child and parent shapes in
case of resizing. A general concept must be introduced.

Original issue reported on code.google.com by NicoPete...@gmail.com on 22 Apr 2008 at 2:20

[GoogleCodeExporter]

will fix issues #5, 6, 7 and 24.

Original comment by NicoPete...@gmail.com on 22 Apr 2008 at 2:22

[GoogleCodeExporter]

Original comment by NicoPete...@gmail.com on 7 May 2008 at 1:48

• Changed state: Started
• Removed labels: Schedule-ShortTerm

[GoogleCodeExporter]

Changing size of pool: only via resizing of the pool. lanes should not change 
the
pool's bounds.
Width of lanes is controlled by width of pool.
height of lane is controlled by resizing the lane. the height of neighbouring 
lanes
is also manipulated so that still all lanes fit into the process.

what happens to shapes inside the lanes?

Original comment by NicoPete...@gmail.com on 7 May 2008 at 2:14

[GoogleCodeExporter]

a lot of improvement in layouting/updating/refreshing has been done (see rev 
#401),
but this is not completely solved.

Original comment by NicoPete...@gmail.com on 27 May 2008 at 8:30

[GoogleCodeExporter]

Original comment by W.Tsches...@gmail.com on 11 Jun 2008 at 1:40

• Added labels: Priority-Medium
• Removed labels: Priority-Critical

[GoogleCodeExporter]

Original comment by NicoPete...@gmail.com on 23 Jun 2008 at 7:04

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by NicoPete...@gmail.com on 8 Oct 2008 at 8:15

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by NicoPete...@gmail.com on 8 Oct 2008 at 8:15

• Changed state: Implemented

[GoogleCodeExporter]

Original comment by NicoPete...@gmail.com on 8 Oct 2008 at 8:37

• Changed state: Verified