Tom Lachecki

Yes - I'll look into that.
Update: Found the oversight - should be fixed in the next build  

Yes - I'll look into that.
Update: Found the oversight - should be fixed in the next build  

Hi All,
We are pleased to make available the next update to the 2.1 beta (2.1.0.1732). This should now be available for you shortly on auto-update.
To set expectations we are now at the point where no additional features will be added to 2.1 before release as we focus on final bug fixing and smaller tweaks to the features already added - the list of those included in this build are below (and also included in the main bug fix list )
Bugs affecting all platforms
Auto-Select Groups Failing to Cycle Through the Complete Layer Stack Drawing a new table does not take selected font into account Line width, column guides and distance from text do not scale when rescaling document Renaming global colour adds a history step of "Set global colour" Resampling/resizing text decorations on a master page increases the width of the decoration, relative to the number of pages Strip Camera Raw crs metadata on export to raster formats Brush accumulation fixes Bugs affecting Desktop (Windows and macOS)
2 page facing document starting on the left cannot export page 2 individually to PDF Attached documents cause app to crash when added as a Book Chapter Edit Embedded PDF > Layer selection through the layers panel does not select the objects and ignores any edits made to it Hang printing a book Preflight Maximum ink setting can wrongly report an error Publisher hangs adding an Index on a book Running headers - add to main menu fields Snapping indicator is offset when drawing objects User File - importing IDML document with embedded EPS files opens with placed resource size of 0x0, EPS files are not displayed When cross-references are updated during export of a book, their values disappear from publication pages Bugs affecting Windows
Expanding multiple entry in resource manager 'jumps' to last manually selected resource First Dash Pattern Gap no longer has a minimum value of 0.05 on Windows Font Manager - Fonts disappear after selecting substitute Running headers end on dropdown has no entries in it Text Contrast doesn't affect Adjustments or renamed layers on Windows Bugs affecting macOS
Adjusting spinners in Character Panel can cause all spinners to stop working Blend Mode Shortcuts: Add is missing a shortcut on macOS Brush panel - brush selection lost when category changed Brush panel - name labels don't scale with font size preference Brush selection highlight is lost when switching categories  Edit Field... Right click option incorrectly available on some fields On the Books panel's Preferences menu, Update Cross-References seems permanently unavailable Bugs affecting iPad
Allow multi-select place in Designer and Photo Add Status indicator to Style Picker Tool Context Bar Brush panel - reverts to Basic category on persona change Don't dismiss Style Picker menu when All / None selected Long pressing a Section Name field in document text displays unnecessary Edit option Menu can go offscreen PDF export issue / lock up on iPad Running headers - add as field on keyboard? Stock Panel - Pixabay has lost the vector option on first run Text Vertical alignment setting is not reflected in the UI

Hi Tom
No they are not thanks for making the change

This has now been fixed in our code; might not appear in the very next beta, but it'll appear.  

We'll strip Camera RAW metadata on export to raster formats (e.g. JPEG).

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

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.

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

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

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!

You guys rock. Thank you for listening to us!

Thank you!

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

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.

This is a common shortcut with some graphics drivers to alter the rotation of the screen; it isn't Affinity doing that  
I recommend checking your nVidia/AMD/etc settings.

Since I live in Arizona I have my camera time set to Mountain Standard time, so I'm not worried about other timezones. But as long as the fix will allow the original timestamp created by the camera to be displayed in the EXIF data, that is all I need.

My first attempt to upload this file failed so here is a 2nd attempt.
Please let me know if it has uploaded correctly.
_DSC4083.NEF

Thanks @Hangman
@AlanV2 That is indeed the same thread I was thinking about. This was closed as 'by design' because EXIF standard states that the Software field is about what created the image (more info here, page 40) and has nothing to do with software that edits it later on. That's what the 'history' fields are for and we do write into those. That was discovered on the older thread.
 

We'll take your feedback on board  

We'll take your feedback on board  

I'm not against marking/tagging fonts, but it's important to fully understand/explain why  they should be marked.  This will help ensure that the resulting change (if made) satisfies the requirements. It has been unclear (to me) whether you were merely concerned that the fonts could not be used in other apps, or were concerned about the legal issues with using them. 
Each concern requires a different design, and different capabilities.

They are, but as part of the .afpackage file, not separately on the Fonts folder.

Yours has no History section, which is where that data is entered. The photo from my screenshot, I did not choose to save history with my image/document. So AP done that on it's own.

I get the History metadata item if in the Export panel I enable "Embed Metadata." If I do that, I get a raw data item like <xmpMM:softwareAgent>Affinity Designer (Sep 22 2019)</xmpMM:softwareAgent," in this instance for a file I last modified in AD 1 on that date.