It somehow says in the docs "there can be only one case associated at the same time", and a switch has to happen by explicitly unassociating the old case.
(whatever "case" means exactly here—but it does seem to contain the attributes to the mesh)
The conjecture was that that may have caused the bug (it appears only without XML file anyways).
It somehow says in the docs "there can be only one case associated at the same time", and a switch has to happen by explicitly unassociating the old case. (whatever "case" means exactly here—but it does seem to contain the attributes to the mesh)
The conjecture was that that may have caused the bug (it appears only without XML file anyways).