skinparam declaration depends on order

[kkrafft1999]

Describe the bug skinparam ActivityBackgroundColor overrides skinparam ActivityDiamondBackgroundColor and skinparam ActivityBorderThickness overrides skinparam ActivityArrowThickness

If I change the order of the skinparam definitaion then it works, But it should make no difference how the skinparam definitions are ordered.

[The-Lum]

[Just for the record] See also plantuml/plantuml#1084

Perhaps use style instead.

Regards, Th.

[The-Lum]

Hi @kkrafft1999, and all,

Yes you have right. Thank for the report. But:

• Could you now use the style new functionally?

From:

@startuml
skinparam ActivityDiamondBackgroundColor red
skinparam ActivityBackgroundColor blue

skinparam ActivityArrowThickness 2
skinparam ActivityBorderThickness 1

if (counter?) equals (5) then
:print 5;
else 
:print not 5;
@enduml

To:

@startuml
<style>
activityDiagram {
  arrow {
    LineThickness 2
  }
  activity {
    BackgroundColor blue
    Thickness 1
  }
  diamond {BackgroundColor red}
}
</style>
if (counter?) equals (5) then
:print 5;
else 
:print not 5;
@enduml

[The order of diamond is always relevant!] 🙄

---

And FYI, see also:

Unfortunately, we won't fix issues in skinparam. Skinparam are still supported for very simple case (and for ascending compatibility) but we would like people to migrate to style instead. (The main reason is that code for skinparam is too old and not very well written).

On:

• https://github.com/plantuml/plantuml/issues/1464#issuecomment-1601464639

---

Enjoy, Regards, Th.

[kkrafft1999]

Thank you @The-Lum , this works for me. :) Thanks for your help. Regards, Konrad.