Closed NathanLovato closed 5 years ago
I missed this. This happens because of:
return path.format(e=ext[0], m=margin[0], s=scale[0])
@Larpon after thinking about it maybe this isn't the right way to do it. What happens if you use c=
metadata with multiple s=
values say? You'd end up exporting for COA the same file multiple times but returning the same filename/file path if it wouldn't give an error. So your COA module would use incorrect paths.
We need to think a bit more how c=
should interact with the other metadata. Should it ignore it, at least margin/scale? (m/s
) should it treat it differently? Plus there's this error when not using c=
, but the other metadata because I'm creating map
objects which can't be indexed with eg. mab_obj[0]
.
For now @NathanLovato, for your own use, you can just comment out that line from Infrastructure.py
or downgrade to the previous commit.
@razcore-art - well right now the support for c=
can actually be removed completely.
I put it there to make it ready for sheet support. The sheet support feature could be made to support margins and scaling. But it'll have to be a function you run after using WNode.save()
. Then find the exported files and combine them into a sheet, collect the meta-data and then delete(?) the exported files used in the sheet and finally join the meta-data with the final json result
I particularly find this section a little frustrating to work out and expand.
Quick fix in #23
Trying to export anything by clicking
All Layers
orSelected Layers
triggers an error. This happens only with the latest master, after the addition of the COA export.Traceback: