Migrate your release version content to beta

[Ash]

Apps: All
Platforms: Windows and macOS

For the convenience of Beta testers we have add an option in preferences to migrate all settings and content you have in your retail versions over the beta versions at anytime. You can find this under the beta menu of preferences.

[MikeTO]

Thank you!

[debraspicher]

You guys rock. Thank you for listening to us!

[Patrick Connor]

Known issues

• HUB-295 - Copying of settings from Release to Beta isn't working on Windows

[MikeTO]

This is minor but for brand new panels like Cross References, this migration feature sets them smaller than their minimum height and their position to something other than the default.

[footeg]

This option is greyed out in Affinity Photo. Windows 11 latest update. Do I need to have all the beta apps installed to see this option?

[Pauls]

@footeg - how is your release version installed (MSIX, Exe, Microsoft Store or direct from Affinity web site)

[Tom Lachecki]

26 minutes ago, footeg said:

This option is greyed out in Affinity Photo. Windows 11 latest update. Do I need to have all the beta apps installed to see this option?

Theoretically it should be available if any v2 release app is installed; it doesn't have to be the same app.

[Tom Lachecki]

28 minutes ago, MikeTO said:

This is minor but for brand new panels like Cross References, this migration feature sets them smaller than their minimum height and their position to something other than the default.

Thanks Mike that's interesting; could be a data file got missed out. Which platform is this on?

[MikeTO]

2 minutes ago, Tom Lachecki said:

Thanks Mike that's interesting; could be a data file got missed out. Which platform is this on?

macOS Ventura

I also wound up in a situation where I couldn't open the cross ref panel - I'd choose it from the menu and it not only didn't appear, the menu item wasn't getting checked. I quit and then reloaded my 2.0.4 settings again a couple of times but couldn't duplicate this issue, but keep a watch out for it.

Btw, now that you've kindly added this feature, it would be nice to go the other way, too. 🙂 I had Publisher 2.1 beta set up exactly as I wanted it with keyboard shortcuts for the new features and with a revised panel layout since I'll be using cross refs all the time and had to sacrifice something else to make room. The shortcuts are easy to migrate back to retail since I can export those but studio panels are a bit more work. We users are a needy bunch!

[Tom Lachecki]

We currently have no plans to implement it in reverse - this would be problematic in many cases. But I appreciate it would be useful!

[footeg]

26 minutes ago, Pauls said:

@footeg - how is your release version installed (MSIX, Exe, Microsoft Store or direct from Affinity web site)

It was the unsandboxed exe download from my account on the Affinity web site as are all the release versions.

[footeg]

21 minutes ago, Tom Lachecki said:

Theoretically it should be available if any v2 release app is installed; it doesn't have to be the same app.

I have all the V2 release apps installed but only the Photo Beta release Tom.

[Tom Lachecki]

The unsandboxed app data paths have changed in the 2.1 beta so it's possible there's a bug here in not picking up the original 2.0 paths from an unsandboxed installation.

[footeg]

That might explain it Tom, thanks. I see the screenshot from Ash's post is from the Mac version of the program. In the Windows version preferences have become settings & the screenshot with Beta Program selected looks somewhat different to the Windows screenshot.

[Gnobelix]

Thanks for the function, it makes things a lot easier.

 

Cheers

[garrettm30]

This ought to be a good convenience to us to help beta testing. Thank you.

However, I have found shortcuts do not seem to have been migrated when I clicked the “Copy Settings & Content From Release App” and allowed it to be restarted. Is that expected? I even tried twice. Curiously, the message that popped up stating “additional disk space required” showed a different amount. The first time, it showed around 176 Megabytes, while the second time it showed 916.8 MB.

I am attaching an export of my Publisher 2 Release keyboard shortcuts that I hoped would be imported into the Publisher 2 beta. The shortcut where I noticed it is that the “home” key on the extended keyboard should have gone to the first page in the document according to my settings.

Afterward, I imported the shortcuts in the older way, and here they were all copied as expected. Then, I tried the new setting migration again, and it replaced my shortcuts again (with I don’t know what) so that the home key no longer worked as I had defined. Could it be that the migration is importing from something different, like maybe one of the other Affinity apps? I am expecting Publisher 2 to Publisher 2 beta.

AffinityShortcut.affshortcuts

[MikeTO]

4 minutes ago, garrettm30 said:

However, I have found shortcuts do not seem to have been migrated when I clicked the “Copy Settings & Content From Release App” and allowed it to be restarted. Is that expected?

Shortcuts were copied for me on macOS.

[Tom Lachecki]

11 minutes ago, garrettm30 said:

Curiously, the message that popped up stating “additional disk space required” showed a different amount. The first time, it showed around 176 Megabytes, while the second time it showed 916.8 MB.

The amount of space currently used by your beta content, which will be deleted, is taken into consideration for this calculation.

[Tom Lachecki]

13 minutes ago, garrettm30 said:

However, I have found shortcuts do not seem to have been migrated when I clicked the “Copy Settings & Content From Release App”

We'll check into this.

[md_germany]

Does not seem to work for me. Could it be because my purchased version 2 is from the Mac App Store? Here the preferences are in >Library>Containers ... . Or should it still work?

[debraspicher]

This is helpful for y'all as well because if we import everything instead of cherry-picking imports, it will offer as much opportunity to showcase bugs across various use cases. So while it's a bother, do add in as much portability as feasible. One of us will have some weird setup that will cause mayhem... no doubt... (edit) so while the convenience is very welcome, it makes our day-to-day usage in beta much more realistic...

[Tom Lachecki]

9 minutes ago, debraspicher said:

This is helpful for y'all as well because if we import everything instead of cherry-picking imports, it will offer as much opportunity to showcase bugs across various use cases. So while it's a bother, do add in as much portability as feasible. One of us will have some weird setup that will cause mayhem... no doubt... (edit) so while the convenience is very welcome, it makes our day-to-day usage in beta much more realistic...

Yes indeed  

[Tom Lachecki]

27 minutes ago, md_berlin said:

Does not seem to work for me. Could it be because my purchased version 2 is from the Mac App Store? Here the preferences are in >Library>Containers ... . Or should it still work?

It should.

[Sonny Sonny]

Thanks, this is the setting i'm waiting for