Jump to content

Recommended Posts

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

Share this post


Link to post
Share on other sites
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.


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.499 Beta

Share this post


Link to post
Share on other sites
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.


Affinity Store: Affinity Suite (ADe, APh, APu) 1.7.3.481.
Windows 10 Pro, Version 1909, Build 18363.476.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
Share on other sites
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.


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.499 Beta

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.