Continuous export checkbox loses state when a file is reopened

[Mason M]

I just figured out how to get continuous export working, and it's hugely helpful, but I've noticed that my export configuration options are erased each time I reopen a Designer file. This surprised me, because ticking the continuous export box marks the file as modified, and saving the files clears the modified marker, which makes it seem like my configuration has been stored.

I searched the forums for help and I found a post in the feature request forum describing the same issue. I know these things are subjective, but I interpreted this behavior as a bug, since it seemed like the program was communicating that it had done something (saving my export configuration) that it actually hadn't.

To provide some context, I'm making figures for a PDF document authored with LaTeX. I used to use Inkscape for this, but I'm trying to switch to Designer. Inkscape can be used as a command-line PDF exporter, so I can generate the full document by running a single script (which can be bound to a keyboard shortcut, run on file changes, etc.). Designer is an upgrade in so many ways, but now it takes 6 clicks, plus navigating to the export directory, to get set up to edit a figure. Even if this someday becomes second nature to me, I can see it being a stumbling block for collaborators.

I think my setup is pretty typical in the science world, and from another post I found it seems like users doing web and app design are struggling with the export workflow as well:

(i.e., if the continuous export checkbox persisted its state, presumably not having a command-line export tool wouldn't be as big of a deal.)

I'm using the Designer Customer Beta version 2.2.0.1954 on Windows 11.

Edited August 23, 2023 by Mason M

[NathanC]

Welcome to the forums @Mason M,

Currently, restarting your app session or closing and re-opening your file will not retain the 'Continuous' checkbox, this is intentional (Regardless of if the file is flagged as modified when altering the setting). This is because the dynamic link between your exported slice(s) path and the app is not retained within the document, which then forces the 'Export Slices' to be actioned again before 'Continuous' can be enabled, so a new file path and link is established.

This will likely be due there being many variables to consider when a document is opened/closed, such as the document file path (or file) no longer being available, differences between the file path between OS platforms, removable storage location no longer available etc.

For the current functionality with continuous export to be changed this would be more of a feature request. 🙂

[Mason M]

Hi @NathanC,

Thanks for clarifying! I'll go ahead and migrate this over to the feature requests channel.

[Anonymous Puddle]

Hi Mason, have you created a feature request on this yet? I would also like to see this feature implemented.

[Mason M]

Hi AP,

I ended up opening this feature request, which was less about the continuous export checkbox specifically and more about the kind of export process I would ideally want (basically, what I've been missing since I switched from Inkscape):

I don't think I opened a feature request for this particular issue, though.

[Anonymous Puddle]

Okay, I submitted a feature request for it, though I like your thinking with your ideas.