Migrate your release version content to beta

[Tom Lachecki]

7 hours ago, woefi said:

Should it not also copy the toolbar arrangement and customized tool box?

Yes - I'll look into that.

Update: Found the oversight - should be fixed in the next build  

Edited March 23 by Tom Lachecki
Added update

[Radosław]

12 minutes ago, Tom Lachecki said:

Shortcuts will be migrated as of the next beta.

Next beta means next version of beta or next beta program?

[Tom Lachecki]

The next version  

[nwhit]

Affirm that Photo does not import the plugins pref, and all apps didn't import the Toolbar pref for Icon & Text.

But THANK YOU, THANK YOU for importing the actual Studio layout from the working versions! That has always been such a PITA having to rest those up. 

[jdvoracek]

This may be by design, but the above option does not copy the left studio tools from the release app 2.0.4. Thank you.

[Intuos5]

It would also be nice if the studios would be imported by default. If I have to go to the list to activate my studio preset that's not that bad, but I prefer not to have to look it up on my drive.

But I am happy the studio preset does apply correctly.

[Intuos5]

I'm also noticing that the preference setting, for show lines in points is not copied over, because it is enabled, while I disabled it (I'm not using the migrate content button).

[aaturner]

Just installed beta version 2.1.0.1781 of all apps on Windows 11 via the .exe (downloaded from the Affinity website), rather than the msix alternative. Pressed the magic "Copy settings & content from release apps" to transfer libraries, plug-ins etc. from v2.0 and to set myself up for a quick start. Unfortunately, everything in the beta versions was removed/reset, with nothing at all transferred.

Is this a solely Windows problem or have I missed an obvious trick and done something silly? This has happened to me once before, resulting in my having to install everything manually.

[DanG]

Unfortunately this feature currently won't work for .exe installs. We had to change the data path for the .exe installations in 2.1. You should find that the .exe installations can be migrated from after 2.1.

[walt.farrell]

31 minutes ago, DanG said:

Unfortunately this feature currently won't work for .exe installs. We had to change the data path for the .exe installations in 2.1. You should find that the .exe installations can be migrated from after 2.1.

But, out of curiosity, what does that mean for the official 2.1 release, using .exe installs? 

Will we have to redo all our setup migrating from 2.0.4 to 2.1 there, too?

[lphilpot]

My concern, too. I've been using 2.1 betas exclusively now, not my 2.0.4 release version (which is still installed). Will there be a way to migrate my beta settings to the 2.1 release version?

[DanG]

On 5/2/2023 at 11:30 AM, walt.farrell said:

But, out of curiosity, what does that mean for the official 2.1 release, using .exe installs? 

Will we have to redo all our setup migrating from 2.0.4 to 2.1 there, too?

Settings etc. should be migrated from 2.0.4 release to 2.1 yes. Unfortunately there is currently an issue which means this isn't working correctly for exe installations, but our development team are currently looking into it.

20 hours ago, lphilpot said:

My concern, too. I've been using 2.1 betas exclusively now, not my 2.0.4 release version (which is still installed). Will there be a way to migrate my beta settings to the 2.1 release version?

I'm afraid this won't be an option no. This feature was designed to make the Beta settings match the Release settings for ease of testing the betas, but won't go the other way.

[aaturner]

Thank you all for your comments. While disappointing, I shall thus stick with using V2.04 for the time being for my main work and play around with v2.1 for testing purposes until the release version is ready. Pity, really, but all part of life's rich tapestry!