Assets shared between Designer and Publisher

[Grzeniu]

Hello!

I am using assets quite extensively across both Designer and Publisher. Is there a way to use one set of Assets that would be updated in any of the applications with as little actions as possible? Ideally like fonts are, i.e without any intervention - when I add anbject to assets in Publisher, it shows up in Designer as well. That sounds too perfect for me and most probably has it's serious disadvantages, but I wondered if there's some workaround.

Maybe, as mentioned in this thread, I should use the Windows junctions functionality and have the assets updated after application is restarted?

Regards,
Grzegorz

[walt.farrell]

15 minutes ago, Grzeniu said:

Maybe, as mentioned in this thread, I should use the Windows junctions functionality and have the assets updated after application is restarted?

While that might work for sharing between two copies of Designer, running one at a time on two separate computers, I predict there might be problems if you tried to use that approach to share the data between two different programs (Designer and Publisher) that might be running at the same time on the same computer.

Each program probably believes it is in control of its files, and you would likely have problems if both were running at the same time, and trying to update the files at the same time.

[Pšenda]

5 hours ago, walt.farrell said:

Each program probably believes it is in control of its files, and you would likely have problems if both were running at the same time, and trying to update the files at the same time.

Concurency access to one file is a fairly standard technique.

[walt.farrell]

2 hours ago, Pšenda said:

Concurency access to one file is a fairly standard technique.

I'm not sure if you mean that multiple processes can concurrently access a file, or some thing else. If that's what you meant, then yes, it's fairly standard but the programs still have to be designed to allow it, and not to make assumptions that no one else has changed the file contents. Given that (as far as I know) only one copy of each Affinity application can run at a time, and given that they use separate directories for storing all their propcol files, the designers might have assumed that allowing for concurrent access wasn't needed.