Dan C

Apologies, I just restarted my mac to install the latest Sonoma update and then tried this again - and have since been able to replicate the issue. I believe the trigger for this depends on your cursor placement when opening the Font switcher menu from the Glyph Browser. Clicking the font name to open the dropdown menu selects the font name as highlighted text, and then using the scroll bar triggers the dialog to immediately close. Clicking the dropdown arrow to the right of the font name, then using the scroll bar works as expected. I'll get this logged with our team now, but can you please confirm @Jonopen that this issue doesn't happen for you if you open this menu from the dropdown arrow? Screen Recording 2024-03-15 at 12.33.19.mp4 @Hangman, I believe this issue will be specific to Sonoma, as macOS have changed these dropdown menus, hence the scroll bar appears differently between our recordings! Many thanks

- Please stop advising other users who should or shouldn't post here on the Affinity Forums, this is the role of the moderation team and not yourself as a user. I'd recommend following the above advice and using the 'Ignore' option if you don't wish to see certain users replies in this thread. ______________ I absolutely understand, and I appreciate you aren't the only Linux user in this boat - I am certain our team will be the first to share any information or plans we have for Linux here on the Forums, if this changes in the future

Thanks for your report @Jonopen! I can confirm that I have tested this using macOS Sonoma on an M1 mac mini and I'm currently unable to replicate the issue you're reporting. Therefore can you please provide a screen recording showing this issue occurring, to ensure I am following the same steps as yourself? Can you also please confirm the device you are using for input when this happens? (ie magic mouse, USB mouse, drawing tablet etc) I can confirm this separate issue is already logged with the team, and I've 'bumped' this with them now

To confirm, I am a moderator of the Affinity Forums - however I'm not a Developer or manager of the Affinity apps, therefore this decision is not mine to make. I can only provide you with the information we are provided with internally, which I will do my best to summarise below: As far as I understand, we have no current plans for a Linux version, and no current intention for this to change. We unfortunately cannot comment on your 'what if' scenarios, as not only would this be purely speculative, any such major shifts in the market would likely require a large overhaul of many software companies, including Affinity - and this isn't something that I believe any company would actively plan for or consider, based on the previous market trends. I am not aware of any current 'goal' or 'criteria' to achieve before the above changes. We are currently interested in continuing to improve and update the Affinity apps across Windows, macOS and iPadOS and are not, at this time, looking to develop for the Linux market. _________ I do not wish for this post to be seen as a 'definitive answer' as to whether we will, or won't develop for Linux in the future, as this isn't something I can personally say for certain. As you may have heard before, "You never know what tomorrow brings" and similar to your hypothetical questions in your original post, no one can ever be truly certain of the future and how the ever changing landscape of software development may move our current ideas.

Again, Affinity may be the trigger of this issue - but certainly isn't the cause. As above you can find out further information on your system as to the cause of this crash at kernel level. If the PC has crashed to a BSOD, all active data is lost. This is unfortunately not something Affinity can control or change. Affinity does include an Autosave file recovery system for if the application has crashed and not the OS - though this should not be relied upon as a backup method. The app will have been unable to create or retain an 'autosave' file when the BSOD occurred, as these are temporary files which are removed when the PC restarts, in order to not retain unwanted space on your drive.

Hi @LeaS, Not to worry, I've moved your thread to the correct 'Questions' section of the forums. When first launching Affinity V1, you should have been prompted if you wish to transfer your custom content from V1 to V2 - provided both apps are installed on the same device. Alternatively, within V2 you can open the My Account dialog (the 'User' icon in the top right) and sign into your Affinity ID. Once signed in you will see a list of all your compatible add-on kits, including the Inksy Street Art brushes. Installing these through the My Account dialog will make the brushes available in Affinity - though please note you will need to be in the Pixel Persona to use these in Affinity Designer. I hope this helps

Hi @Rafael_Morgan, Sorry to hear you're having trouble with this document. Firstly, I understand this is an important issue to you - but please do not post a thread on the forums, email the support team and directly DM a moderator simultaneously when requiring support. This can mean multiple members of the support team are trying to solve your issue across different methods (often without being aware of the others efforts) and can actually decrease the speed at which we're able to assist. Thanks for your understanding here. Secondly, the Affinity apps aren't able to cause a 'Blue Screen of Death' in Windows, as they are user-mode applications. Only kernel-mode applications (i.e. drivers) are capable of this. Applications, including Affinity, make use of these drivers which is why it appears some "applications cause BSOD", but in reality the application itself is unable to cause this, but might have been the trigger. Inspecting your document within a HEX editor, I can see that a large amount of the data within the file is missing, indicated by a '00' HEX value: It's likely due to this BSOD that the file was not written successfully and the data corruption occurred - unfortunately our team are unable to recover completely missing data, as it simply is no longer present in the file, our apologies. As above, we recommend creating regular backups of any documents you are working on, as unexpected issues may occur and are unfortunately out of our control. I would also recommend checking the Event Viewer / System logs on your PC regarding the BSOD that occurred, as this can indicate driver / Windows corruption or in worst case scenarios can be an indication of failing hardware. I hope this clears things up and our apologies once again we can't assist further here with your file.

Hi @pat fern, Sorry to hear you're having trouble following the update, however we're going to require further information to assist you here. Is the application crashing when editing a specific file or following a certain workflow? If so, please include a copy of your file or description of your workflow here. In regards to 'not saving' - can you please expand on this for me? Are you seeing an error when trying to save, or does the save dialog not appear to show at all for you? The more information you can provide, including screenshots or a screen recording if necessary can help us to resolve this for you. Many thanks in advance

Hi @Manjinder Singh, Sorry to hear you're having trouble! Can you please provide a screen recording showing the exact steps you're taking when this occurs, so that I can investigate further and report this to our team? If you're unsure how to take a screen recording, please see our below FAQ - Many thanks in advance

Hi @PerryM, Thanks for your post & I'm glad to hear you've been able to resolve this issue with a CTRL reset. Are you able to confirm the exact search location you added to cause this issue within Affinity? As I would like to get this logged with our team for further investigation. Many thanks in advance

That's wonderful news, many thanks for letting us know! The issue regarding 'Tagged PDF' export has already been fixed by our team in an internal build and will be available in a future update - though of course you can continue to use the workaround of disabling this option when exporting, in the meantime

You're very welcome, I'm glad to hear this helped!

Sorry to hear you're having trouble @EPriuli! I believe I can identify the issue from the PDFLib.log provided (thanks for this!) - it appears to be a known issue when exporting to PDF with 'Tagged PDF' enabled, if you have a text object that has been cropped with a vector mask. Please navigate to File > Export > PDF and then untick Tagged PDF in the Export settings: Does this now export as expected please?

The Metadata Studio has a dropdown menu to select Categories - which provides access to other options where you can add/edit the Metadata as required: 2024-03-14 12-52-07.mp4 Secondly, the screenshots shown in your image are still for Affinity Photo V1. You can find the Affinity Photo V2 help file for metadata here: https://affinity.help/photo2/English.lproj/index.html?page=pages/Panels/metadataPanel.html&title=Metadata panel

When creating a new file and using File > Save, or File > Save As, the application has to prompt for a file name and location - as you haven't previously set this for the file. If you have a file that has been previously saved on your system, File > Save will not prompt for a name or location, but File > Save As will. This is correct and expected behaviour, following the convention of most other apps. I hope this clears things up!

Hallo @Hanjoerg, Es tut mir leid, dass Sie Probleme haben! Grundlinienraster können für das gesamte Dokument und je nach Bedarf separat für jeden einzelnen Textrahmen festgelegt werden. Wenn Sie über ein Dokument-Grundlinienraster und ein Textrahmen-Grundlinienraster verfügen, sind beide gleichzeitig sichtbar: 2024-03-14 12-36-04.mp4 Ich hoffe, das klärt die Sache

Thanks for your post @martinhb! I can confirm that in Affinity Photo V1, the Studio options were found under the View menu. In Affinity Photo V2, the Studio options are found under the Window menu, as shown in your screenshot. Equally, your screenshot shows that the Metadata Studio is already enabled (ticked) and is displayed on the right hand side of your screen: I hope this clears things up

You can use ESC to cancel text editing, then use the V shortcut to switch to the Move Tool - 2024-03-14 10-41-21.mp4 It's hard to be certain - from the screenshot above it may be that your text decorations are being imported as 'lines': One option could be to create a Curve in your document using the Pen Tool, setting the Stroke width to 0.125". You can then use Select > Select Same > Stroke Weight > Less (or Equal) and the app will automatically select objects with this stroke weight or less: 2024-03-14 10-43-30.mp4 I hope this helps!

Hi @Dimenta, With the Colour Chooser window opened and 'in-focus', keyboard shortcuts will not be detected - however if you simply click / right-click on the canvas with the Colour Picker dialog open, you can then use Shortcuts as required

Welcome to the Affinity Forums Please email affinity@serif.com if you wish to have your Forum account deleted. Many thanks!

Many thanks for providing that for me! I can confirm I'm able to open and edit this document here in 2.4 Windows without issue - as well as open additional files alongside this document, so I'm not entirely certain why this is causing issues for you locally at this time. I appreciate you have currently 'rolled back' to 2.3.1, however I will be returning 2 different versions of your file to you now through Dropbox, which I have recreated using different methods. If you are willing, you can try updating to 2.4 once again, then loading either of these files to see if the behaviour is improved. As the files have been recreated, I recommend carefully checking these to ensure that objects have not been lost/moved during the process. I hope this helps

If it's there it seems well-hidden. I believe this is covered in the Placing Content page, although it could perhaps be made clearer - (note the shortcut is Alt on Windows )

Hi @Hans Chiu, As I understand it, when selecting 'No' to this option, the .autosave file is discarded from the temporary folder on your system. You can manually locate these .autosave files, provided the app has not yet discarded them - though the location will differ based on the following: Are you using Windows, macOS or iPad? If you're using Windows - are you using the MSIX or EXE installer? Many thanks in advance

Thanks for letting us know @Tangot2 & I'm sorry to hear this! I can confirm that our team are aware of an issue with the EXE versions of Affinity V2 essentially uninstalling and reinstalling during update - which causes the desktop shortcut or 'pinned' taskbar icon to become a page icon and no longer be usable, requiring a new shortcut or pin to be created by the user. This is logged with our development team and we're hoping to have this resolved in a future update. I'll be sure to 'bump' this with our team not to bring it to their attention once again. I hope this clears things up

Thanks for confirming that for me! I've been able to replicate this here and I'm getting it logged with our developers now as this dialog should either resize to fit - or be user resizable to stop this from occurring. I hope this helps