You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are facing an issue that in some model the diagram cache contains several svgs with case sensitive duplicates. Means under windows this fails to use:(as same files will be overwritten )
Is there a flag or approach to avoid/fix this?
Under Unix/Docker the scripting works. Developing the exports with capellambse diagram cache under Windows brings us issues.
The svg diagrams are really not the same and partly even in different layers. Partly 3 duplicates in one model.
The text was updated successfully, but these errors were encountered:
There's no easy way to prevent that, as those are the exact IDs used to distinguish between the diagrams internally. However, if you want to only use the diagram cache on Windows, you can work around the issue by packing all the exported diagrams into a *.zip file (while still inside the Docker container) and directly using that archive:
The exporter script on the other hand currently only supports writing to local directories. It would first need to be migrated to use the FileHandler abstractions (which is a manageable amount of effort - all of the related code should be in capellambse/_diagram_cache.py), and we also need to implement write support in the ZipFileHandler (which should be relatively easy, as it basically just needs to forward the calls to the stdlib zipfile module).
We are facing an issue that in some model the diagram cache contains several svgs with case sensitive duplicates. Means under windows this fails to use:(as same files will be overwritten )
Is there a flag or approach to avoid/fix this?
Under Unix/Docker the scripting works. Developing the exports with capellambse diagram cache under Windows brings us issues.
The svg diagrams are really not the same and partly even in different layers. Partly 3 duplicates in one model.
The text was updated successfully, but these errors were encountered: