"allowmixing" has side-effect on remove

Question

When "allowmixing" is set on a diagram, then the "remove" command does not work on nested elements.

With PlantUML v1.2022.6 it worked, I haven't tested versions in between.

Example:

@startuml

' toggle allowmixing on/off to see
' the side-effect.
allowmixing

node "huhu" as huhu {

rectangle "trara" as trara

}

' when allowmixing is on, then the remove
' command on the nested element has no
' effect.
remove trara

@enduml

Comments

btw. the same problem with the "hide" command...

Answer 1

Hello D.,

Same answer as:

• https://forum.plantuml.net/19823/allowmixing-has-side-effect-on-remove?show=19843#c19843

If you use `allowmixing` and potentially class and namespace...

To remove/hide, you must use:

• set separator none

• or explicitly the full namespace, like `remove huhu.trara`

Enjoy,
Regards,
Th.

Answer 2

Even if not using "allowmixing", the following code creates a valid diagram (although it should not be possible to mix components and classes (same with object)...

So it seems to be a problem that occurs when mixing class (obj) elements with other (e.g. component) elements onto one diagram which should raise an error I guess, but renders, but then creates a problem with remove and hide...

When introducing "allowmixing" it would be valid to mix these elements, but still the problem with remove and hide remains...

@startuml

component "huhu" as huhu {

class "trara" as trara

}

remove trara

@enduml

Comments

Hello D.,

That is normal, due to namespace management...

With new version of Plantuml, If you must remove trara, you must use either:

@startuml
component "huhu" as huhu {
  class "trara" as trara
}
remove huhu.trara
@enduml

Either:

@startuml
set separator none
component "huhu" as huhu {
  class "trara" as trara
}
remove trara
@enduml

Enjoy,
Regards,
Th.

---

Thanks, that's it!

---

I wrote something wrong here before, seems I cannot delete it so I changed it to this...

Answer 3

It seems it is already worked on for a longer time, unfortunately not yet solved...

https://github.com/plantuml/plantuml/issues/1769