ArrowThickness not applied with stereotypes

0 votes
asked Oct 27, 2021 in Bug by UGxhbnRVTUw (160 points)

Hi,

In this first example, all is fine.

@startuml Without stereotype
skinparam ArrowThickness 5

component toto
component tutu

toto -> tutu <<mystereotype>> : Foo
@enduml

But if I use stereotype, my personalisation is lost.

@startuml With stereotype
skinparam ArrowThickness<<mystereotype>> 5

component toto
component tutu

toto -> tutu <<mystereotype>> : Foo
@enduml

My version : 1.2021.7

Regards,

commented Oct 27, 2021 by The-Lu (64,340 points)

Hello U.,

A possible workaround is to use:

@startuml
component toto
component tutu

toto -[thickness=5]> tutu : Foo
@enduml

If that can help,
Regards,
Th.

commented Oct 28, 2021 by UGxhbnRVTUw (160 points)
My use case is to highlight links according to their type, turn by turn.
Same code, but different points of view.

So, I won't be able to edit each link manually for each version.
That's why stereotypes looks interesting.

But thanks for the idea.

1 Answer

0 votes
answered Oct 28, 2021 by The-Lu (64,340 points)
selected Nov 2, 2021 by UGxhbnRVTUw
 
Best answer

Hello all,

As for:

You can also just use variable, as:

@startuml
component toto
component tutu
component tyty

!$mysthickness="thickness=5"

toto -[$mysthickness]> tutu : Foo
toto --> tyty : Bar
@enduml

If that can help,
Regards.

commented Oct 29, 2021 by UGxhbnRVTUw (160 points)
Even better than previous post, as this notation is shorter than functions.

Thank you !
...