JeffreyK

Just had the same thing, it was on the top of my second screen and to top that, only the left edge of the window was visible. ha! Well, thanks for your answer, it made me check more carefully.

This post is designed to be an aid to knowing if you are using the latest version of Affinity Version 2 applications on your platform.  The thread is now locked so if you "follow" it you will know then we release a new version on any platform. Version numbers are displayed on the About dialog (or preferences in iPad builds)
NOTE: I will update/edit this first post as new releases are added.
Product Name       | Purchase Store  | Platform   | Version | ===============================|=================|===================|===============| Affinity Designer 2 | Affinity Store | Windows 10, 11 | 2.4.2 (.2371) | Affinity Designer 2 | Microsoft Store | Windows 10, 11 | 2.4.2 (.2371) | Affinity Designer 2 | Affinity Store | macOS 10.15-14 | 2.4.2 (.2371) | Affinity Designer 2 | Mac App Store | macOS 10.15-14 | 2.4.2 (.2371) | Affinity Designer 2 for iPad | iPad Store | iPadOS 15,16,17 | 2.4.2 (.2371) | _______________________________|_________________|___________________|_______________| Affinity Photo 2 | Affinity Store | Windows 10, 11 | 2.4.2 (.2371) | Affinity Photo 2 | Microsoft Store | Windows 10, 11 | 2.4.2 (.2371) | Affinity Photo 2 | Affinity Store | macOS 10.15-14 | 2.4.2 (.2371) | Affinity Photo 2 | Mac App Store | macOS 10.15-14 | 2.4.2 (.2371) | Affinity Photo 2 for iPad | iPad Store | iPadOS 15,16,17 | 2.4.2 (.2371) | _______________________________|_________________|___________________|_______________| Affinity Publisher 2 | Affinity Store | Windows 10, 11 | 2.4.2 (.2371) | Affinity Publisher 2 | Microsoft Store | Windows 10, 11 | 2.4.2 (.2371) | Affinity Publisher 2 | Mac App Store | macOS 10.15-14 | 2.4.2 (.2371) | Affinity Publisher 2 | Affinity Store | macOS 10.15-14 | 2.4.2 (.2371) | Affinity Publisher 2 for iPad | iPad Store | iPadOS 15,16,17  | 2.4.2 (.2371) | _______________________________|_________________|___________________|_______________| [Please note that Microsoft Store presents the build number within the store differently so Affinity Store build 2.4.2.2371 appears as a Microsoft Store build number 20402.2371.0.0]
Legacy: For the latest version 1 releases please see this earlier thread
Patch Release notes
The fixes in 2.4.2 are in this post
 
Affinity Designer 2 for Windows (2.4.2)  previous patches: (2.4.1), (2.4.0), (2.3.1) , 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3  Affinity Designer 2 for macOS (2.4.2)   previous patches: (2.4.1), (2.4.0), (2.3.1), 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3   Affinity Designer 2 for iOS (2.4.2)   previous patches: (2.4.1), (2.4.0), (2.3.1), 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3, 2.0.2   Affinity Photo 2 for Windows (2.4.2)   previous patches: (2.4.1), (2.4.0), (2.3.1), 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3   Affinity Photo 2 for macOS (2.4.2)   previous patches: (2.4.1), (2.4.0), (2.3.1), 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3   Affinity Photo 2 for iOS (2.4.2)   previous patches: (2.4.1), (2.4.0), (2.3.1), 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3, 2.0.2   Affinity Publisher 2 for Windows (2.4.2)   previous patches: (2.4.1), (2.4.0), (2.3.1), 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3   Affinity Publisher 2 for macOS (2.4.2)   previous patches: (2.4.1), (2.4.0), (2.3.1), 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3   Affinity Publisher 2 for iOS (2.4.2)  previous patches: (2.4.1), (2.4.0), (2.3.1), 2.3.0, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.3, 2.0.2  Installation of Software and Updates
If you’ve purchased from the Affinity Store— each time you start the software it will check for updates and offer to download and install any available update. For the macOS release, in the application main menu there is an option "Check for Updates". Alternatively, you can download the latest installer by logging into the affinity store here and find the order in your account and use the "download" button in there. Updates are installed automatically (or manually by installing the new version over the old) Previous builds do not need uninstalling first. New installations of paid software downloaded from the Affinity Store requires LICENSE ACTIVATION to use.
Software downloaded from the Mac App Store, Microsoft Store and iPad store do not require a license activation and are updated through the relevant store: 
If you’ve purchased from the Mac App Store— updates are done automatically next time you run your software after it is available in the Mac App Store. However, you do need to be logged in with the same Apple ID you used to buy them. If this does not happen for you, open the Mac App Store app and go to the Updates page and then Store > Reload page or press CMD+R. This should hopefully force the update to show. Apple sometimes phase roll outs around the world which can mean it may take up to 72 hours for your update to be available.
If you’ve purchased from the Microsoft Store— Microsoft Store updates are done automatically by the operating system (each time you start the application). If this does not happen for you, open the Windows Store app and click the three dots in the top right corner of the app and then go to Downloads and Updates. Click Get Updates. This should hopefully force the update to show.
If you’ve purchased from the Pad Store— Your Affinity iPad apps should update automatically next time you run them. However, you do need to be logged in with the same Apple ID you used to buy them. If the automatic update does not happen for you, go to the iPad Store app and go to Updates. Once you’re there, tap near the top of the screen where it states 'Updates' and then hold, pull down and then release. This should manually refresh the updates page. However, don’t contact us if the updates are not available for you yet—Apple sometimes phase roll outs around the world and this can take up to 24 hours.
----------
This thread is locked and will only be posted to by Serif Staff as the released versions change.  Please follow this thread if you want to know about future version changes. If you think this post has got behind and needs updating please PM me.
If you are looking for the beta builds please see these forums 
https://forum.affinity.serif.com/index.php?/forum/32-beta-software-forums/
 
 

PDF password protection has now been added to the 2.2 beta:
If you would like to try this feature before release you can join the beta program here:  https://affinity.serif.com/affinity-beta-program/
 

D'oh! I should have thought of that - It was lurking in the corner of my inbox on the second monitor. Thanks Garry.

Can't select curve nodes using box drag selection in Publisher 2.0.0 on old .apub files.
-Works fine with a new document in Publisher 2, 
-Works fine in standalone Designer using old .apub files
-Works fine with EMBEDDED curves (in a new tab)
-Box selecting any other in-document curve doesn't work with old .apub files
It doesn't seem to matter if the nodes are edited using the corner tool or not.
I'm on Windows 10

It is a bit of a mixed bag right now, in this initial 2.0 release.
There are indeed some important additions, such as footnotes/endnotes, as well as some very nice smaller touches (such as being able to drag the FX icons between layers to copy the layer FX from one to another).
Sadly there are also a few important things that were dropped, such as separated mode on the Mac (this makes little difference to me personally right now but it will be a major impact on many other users, as the "replacement" is simply not practical for many situations and workflows) and the ability to unlock the software offline (which will impact anyone who needs to keep their working computer off the internet for security reasons).
Not everything was added that we might have hoped for, the UI reskin has both positive and negative aspects to it (some of which will vary depending on who you ask), but for the most part and for many users it is a solid upgrade, though not nearly what the hype would suggest.
For some users it is no longer a viable tool for working where version 1 might have been, for others it is a major step forward, depending on the specific needs of that user.

There will be customer betas here on these forums very soon. Be as critical as you like and we would appreciate your credentials improving the software.

Pros:
MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). MSIX promises a 99.9% success rate.  MSI requires admin privileges to install. MSIX installs per-user, but files are deduplicated so that disk space isn't wasted. MSI apps are not sandboxed from other applications, meaning other applications can break those apps (we have seen this with several third-party apps in the past). MSIX apps are sandboxed to prevent this. MSI updates require a manual download of the full ~550mb installer which must be manually installed. MSIX can perform in-app delta updates which are smaller and faster. MSI updates can only be performed one at a time. MSIX can update all three apps simultaneously. MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install. MSIX installs are segregated and don't rely on the registry or special filesystem locations meaning an uninstall always leaves you in a clean state. Installation and app data paths are cleaned on uninstall. MSI apps cannot integrate with Microsoft Photos app to provide "Edit In..." style features. MSIX can. MSI does not require a digital signature. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us). Cons:
MSI can allow the user to change the installation directory. MSIX can move installed apps to different drives, but it cannot choose a specific directory (due to the sandbox). See below: MSI can allow an option to install a desktop shortcut. MSIX doesn't provide this as an option, but you can pin the apps to either the Start Menu or the Taskbar. There is also the secret Shell:AppsFolder location in Explorer that allows you to right-click or drag the icon to your Desktop for a shortcut as a workaround if you need it.  MSI has easy discovery of undocumented app locations for launching from a third-party. MSIX hides the install location due to the sandbox, but we use App Execution Alias to enable this scenario. You can find the aliases in the following location: C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias , and the next post includes aflaunch.exe as a work around if you need that instead. 
 

Still present in Affinity Designer 1.10.5.1342 on Windows. Produces inconsistent results as well as seen in the internal corners. Please fix this as soon as possible. 
Correction: *because in the screenshot. 

I was looking for a solution for large files exporting as PDF from affinity publisher. I found a solution and it may be useful to someone. I export a pdf file and use 200 DPI (the file size is 19 mb). Then I open the saved pdf file in publisher and choose export as PDF again choosing 200 DPI (the file is 1.97 mb) and the quality is the same.

By now, I feel like this feature is hidden somewhere, because they must have added it, right?
The fact that the programme is much lighter and sticks to the essentials is amazing to me, but, as others have said, this feature is the difference between "good" software and a gamechanger (maybe just state of the art, nowadays).
Please, keep up the good work and don't make me regret purchasing the 3 programmes

Its 5 years later and this thread is still valid. What do we need to do to get this a bit higher on the development list? Its a basic feature, I use it most often to clean up logos I pull down from the net. The jagged edges mean I have to use other software for this.

I think it might actually have something to do with the memory leak issue that's been mentioned in other posts. Whenever I start getting lag now, I just save and restart the software to make it go away for a good while again.

Maybe the Export Persona would be better suited for your needs
(but I can't be sure without a test file)

Right now the TOC creation is very hands-on almost completely manual labour because Publisher gets in the way so much. It's atrocious to be kind about it. Also it doesn't create proper PDF TOCs but bookmarks, they show up where the consumer doesn't expect them (in bookmarks instead of the TOC area). This creates unnecessary support tickets.
The document sections aren't honoured at all in the TOC creation. The TOC tool itself is quite barren in terms of usefulness. There is no way to define parent/child relations of headings at all. It's all just a jumbled up pile of text boxes that's loosely referenced by anchors that may or may not be placed in the right area. Sometimes the automation even gives me a bunch of page number entries that I have to manually take out again.
This area of Publisher is seriously bad. It's the worst TOC creation tool I've used since TOCs were added to the PDF spec. It needs a lot of work before Publisher can be used for end user products.

So ... the funny thing is, if you open in Publisher and show non-printing characters, then switch back to Designer they stay on. I found this while trying to get rid of them. haha!

EMF/WMF is broken at least with Office 2016 for me. You are welcome to contribute your bug report to this thread as well.
Black live matter,
mumbojumbo

Thanks for that - I've been able to reproduce that and will get it passed on, however we cannot give time scales on fixes as issues are not always easy or simple to fix. 
 

Unfortunately, this is not mentioned in the Help - https://affinity.help/photo/en-US.lproj/pages/Panels/clrPanel.html

And interestingly, it's different in every Help - which is a little confusing.

Hi Pšenda,
Only the Sliders view (Colour panel's menu) has the dropdown with the colour modes, The Wheel view doesn't have them. The image where the padlock is missing is outdated. I'm logging this to be looked at. Thanks for bringing this up/spotting it.

Yes, I understand that.
I mentioned this because the Help of each application describes the Colour Panel in a different way - see the mentioned Sliders vs Wheel, which I find strange (I would expect that due to the same function and appearance in all applications, their description will be the same).

Hypothesizing here:
The "ti" combination would commonly produce a ligature of some sort.  When the PDF file was written chances are the ligature was given a single code point which happens to map to that particular variant of the letter "e" in whatever encoding the PDF claimed to be in.  If the font was embedded with the document the ligature could have simply been substituted for an unused code point and would have rendered correctly (which is the true purpose of a PDF file - to look good as-is, not to be easy to edit; it is "digital paper" not a proper editing format), but when imported into the Affinity product, which does not use the embedded font, it would have read it as the "e" character and used that instead of the ligature that was encoded in the PDF?
Note that this form of substitution would make sense if it allows the application to use a single-byte encoding for the text instead of a multi-byte one, as this in theory saves space and reduces the size of the PDF file with no impact to its visual appearance - again, the primary purpose of a PDF file which is not produced for reasons of accessibility or searching.  My guess is that if you opened that PDF in Preview / Acrobat Reader / some other PDF viewer with search capability and tried searching for one of the words that has "ti" in it, it probably wouldn't come up in the search either.

Wrong.

Its 5 years later and this thread is still valid. What do we need to do to get this a bit higher on the development list? Its a basic feature, I use it most often to clean up logos I pull down from the net. The jagged edges mean I have to use other software for this.

No, the machine has to serve the human, not the other way ’round. The software/UI has to do what the users want and if the users want a crop tool, give it to them! Especially since a “crop/trim canvas” function would be a tremendous time saver as opposed to going into document setup.
 
For example: I have three small objects on a large canvas (no artboard) and I want to export these three objects as one image — crop/trim canvas (better yet with a shortcut) and hitting Ctrl/Cmd-X would be a thousand times faster than selecting all objects to look at the transform panel and find out the dimensions, then unselecting them, going into document options, entering the dimensions, setting the scaling behavior, and then exporting the image. Likewise, using the export persona for such a simple operation is overkill because you still have to perform multiple steps just for a quick export.
 
The workflow problem is currently prevalent. That you can’t imagine the use of a cropping function doesn’t mean that everybody else is at fault.