From 9fe1686e406a728f03cea8a27b26b67d08d228bd Mon Sep 17 00:00:00 2001 From: HeinrichAD Date: Mon, 31 Jul 2023 22:09:30 +0200 Subject: [PATCH] define -> arrows as request and <- as response Instead of defining that every message from the left to the right side is always a request and every message from the right to the left side is always a response, I propose to used the arrow direction from the PlantUML diagram code. Each arrow with the arrow direction on the right (`->`) is a request and each arrow with the arrow direction on the left (`<-`) is a response. This way the users can define themselves what is a request and what is a response. --- src/net/sourceforge/plantuml/skin/rose/ComponentRoseArrow.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/net/sourceforge/plantuml/skin/rose/ComponentRoseArrow.java b/src/net/sourceforge/plantuml/skin/rose/ComponentRoseArrow.java index 809f1943a..e00dc5170 100644 --- a/src/net/sourceforge/plantuml/skin/rose/ComponentRoseArrow.java +++ b/src/net/sourceforge/plantuml/skin/rose/ComponentRoseArrow.java @@ -185,7 +185,7 @@ public class ComponentRoseArrow extends AbstractComponentRoseArrow { } private boolean isBelowForResponse() { - return belowForResponse && getDirection2() == ArrowDirection.RIGHT_TO_LEFT_REVERSE; + return belowForResponse && getArrowConfiguration().isReverseDefine(); } private void drawDressing1(UGraphic ug, ArrowDressing dressing, ArrowDecoration decoration, double lenFull) {