Search the Community
Showing results for tags 'reusable'.
In short: Slices ought to be retained in Data-merge generated files and propagated in generated pages. Scenario: User sets up a work file using Publisher and Designer tools. Using Publisher, 'Data Merge' is essential to position and populate the file with variables. Using Designer, slices are set up in the same file so that, once data merge file is executed, files can be exported quickly. Data is imported, looks fine, user executes 'Data Merge manager' -> 'Generate'. Generated file looks fine at first but in Designer slices setup is gone! Replaced with UID-looking whole-page slice. Slices cannot be copy/pasted (not clear why, when it could save time in setups and dimensioning), User has to come up with workarounds. Workarounds will increase possibility of error and timewaste. Why is this a problem? This behaviour is detrimental for user since it: results in unnecessary loss of user data and time, requires generation of slices for each future data-merge generated file, requires potentially problematic workarounds. Expected behaviour: Slices are retained in data-merge generated file. This behaviour would be then coherent with retention of text-styles, master pages, swatches, preferences, and other user-set file characteristics and assets in data-merge generated files.
I've recently switched from Adobe CC to the Affinity suite. One thing that I really rely on in InDesign is the Libraries function, so that I can save groups of layout items that I reuse frequently and then just drag and drop them onto whatever document I'm working on. I use it mostly for interface mockups, so there's a lot of toolbars, buttons, icons, menu objects etc that I need to frequently reuse. Neither the Symbols nor Assets functions seem to be exactly what I'm looking for. It isn't about managing imported graphics nor is it about updateable placeholders, it's about reusable sets of geometry, tables and text boxes with effects settings saved with them. Is there anything like this in Publisher? If not, is it on a roadmap for a future release? (And yes, it'd be really cool if it could sync between machines via iCloud or Affinity's own sync service).