Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<<boundary>> stereotype colors/skinparams not changeable #48

Closed
christo-ph opened this issue Mar 8, 2020 · 3 comments
Closed

<<boundary>> stereotype colors/skinparams not changeable #48

christo-ph opened this issue Mar 8, 2020 · 3 comments
Milestone

Comments

@christo-ph
Copy link

Hi,

I am trying to manipulate the <> stereotype font color or size, but it seems to have no effect. All other types working correctly.

No matter what I do, the stereotype remains here white and the size remains default:

image

what I currently have for styling:

!define BORDER_COLOR      #333333
!define FONT_COLOR        #333333

skinparam rectangle<<boundary>> {
  Shadowing false
  StereotypeFontSize 0
  StereotypeFontColor FONT_COLOR
  FontColor FONT_COLOR
  BorderColor BORDER_COLOR
  BorderStyle dashed

Thanks for your help.

@adrianvlupu
Copy link
Member

There seems to be an issue with plantuml itself, maybe I'm missing something but check out this example:

@startuml test
skinparam rectangle<<outerbox>> {
    FontColor #FF0000
    BackgroundColor #00FF00
    StereotypeFontSize 40
}

skinparam rectangle<<box>> {
    StereotypeFontSize 40
}

rectangle "Box" <<outerbox>>{
    rectangle "Nested" <<box>>
}

rectangle "Box2" <<outerbox>>
rectangle "NotNested" <<box>>
@enduml

test

The moment you nest them, the stereotype properties are ignored for the parent element. I think this is the best place to start playing with the properties and maybe you could find something that works. I tried a bunch of combinations but nothing seems to do the trick.

@christo-ph
Copy link
Author

I am going to close this. It is PlantUML related, and according to their announcement, in favour of their new styling system there will be no further time spend on skinparam syntax.

@kirchsth
Copy link
Contributor

@christo-ph: the problem can be solved if you change the package<<...>> stereotype too (rectangle does not set all; details see #128).

@startuml
!define BORDER_COLOR      #333333
!define FONT_COLOR        #770000

skinparam rectangle<<boundary>> {
  Shadowing false
  StereotypeFontSize 30
  StereotypeFontColor FONT_COLOR
  FontColor FONT_COLOR
  BorderColor BORDER_COLOR
'  BackgroundColor #00EEEE
  BorderStyle dashed
}

' skinparam package<<boundary>> {
'   StereotypeFontSize 30
'   StereotypeFontColor FONT_COLOR
'}

rectangle "Box" <<boundary>>{
    rectangle "Nested" <<boundary>>
}

rectangle "NotNested" <<boundary>>
@enduml

@startuml
!define BORDER_COLOR      #333333
!define FONT_COLOR        #770000

skinparam rectangle<<boundary>> {
  Shadowing false
  StereotypeFontSize 30
  StereotypeFontColor FONT_COLOR
  FontColor FONT_COLOR
  BorderColor BORDER_COLOR
'  BackgroundColor #00EEEE
  BorderStyle dashed
}

' that all boundaries have the same init color as the normal rectangle
' (but as soon you change the rectangle background color the package background color is updated too
' and you don't need to set the color in plantUML context)
skinparam packageBackgroundColor #FEFECE

skinparam package<<boundary>> {
   StereotypeFontSize 30
   StereotypeFontColor FONT_COLOR
}

rectangle "Box" <<boundary>>{
    rectangle "Nested" <<boundary>>
}

rectangle "NotNested" <<boundary>>
@enduml

BR Helmut

kirchsth added a commit to kirchsth/C4-PlantUML that referenced this issue Mar 19, 2021
kirchsth added a commit to kirchsth/C4-PlantUML that referenced this issue Mar 20, 2021
… StereotypeFontColor problem (2 - fix update with missing font/bg color too)
adrianvlupu added a commit that referenced this issue Apr 3, 2021
#133, #48: fix StereotypeFontSize 0 and StereotypeFontColor problem
@Potherca Potherca added this to the v2.0.0 milestone Apr 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants