From: SourceForge.net <no...@so...> - 2012-08-02 14:16:44
|
Bugs item #3199693, was opened at 2011-03-04 07:08 Message generated for change (Settings changed) made by mbezdeka You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3199693&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None >Status: Closed >Resolution: Fixed Priority: 7 Private: No Submitted By: Radek Sedláček (rsedlac) Assigned to: Martin Bezděka (mbezdeka) Summary: Changing the length of instances - configuration Initial Comment: It must be configurable whether messages connected to instances 1. move proportionally as the instances are being prolonged/shortened or 2. they keep their position. In both cases the messages must remain connected. ---------------------------------------------------------------------- Comment By: Martin Bezděka (mbezdeka) Date: 2011-12-12 05:14 Message: Since r1228 all newly added messages will be anchored always to instance head. Instance prolonging (dragging the instance's end) will not change message position. ---------------------------------------------------------------------- Comment By: Ondřej Bouda (obouda) Date: 2011-11-30 13:54 Message: Changing the priority to 7, as there is a workaround by using repaint. ---------------------------------------------------------------------- Comment By: Ondřej Bouda (obouda) Date: 2011-11-09 10:53 Message: Even if configuration is not needed, the behaviour should be consistent. Currently, in some cases, it happens that a message end point (message send or receive event) is anchored to the bottom of the corresponding instance, while other message events are (correctly) anchored to instance heads. See the attached examples: - Bluetooth-sample.vsd - Bad-anchors2.vsd - Bad-anchors3.vsd (here, the last message receive event is anchored to the bottom, but after adding another message underneath it between the same instances in the same directions, both messages are anchored incorrectly, whereas adding that message in the opposite direction implies bad anchoring only of this lastly added message and the previous is suddenly OK) - Bad-anchors4.vsd - example of message send event anchored incorrectly Either way, after reattaching the messages to the instances by hand, even in exactly the same point on the instance, they get anchored to the instance head (as expected). ---------------------------------------------------------------------- Comment By: Radek Sedláček (rsedlac) Date: 2011-05-18 00:26 Message: Configuration is not needed. Automatically connected messages shall keep their position when the instances are being prolonged/shortened. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3199693&group_id=219467 |