Sean P

I understand that, however this forum is specifically relating to issues with the version 2 beta.

Just to add these two are currently displaying fine in Affinity for me, however the others are as described.

Thanks all - I will get these issues reported and passed on to development.

I've moved the off-topic discussion about the flag here to keep the relevant issue on-topic.

Hi AP-, As Walt has described this behaviour is by design. However there is an dropdown option in Settings > Tools to change it to Automatic (behaviour as above), Always Constrain or Never Constrain.

Also instead of creating a new threads about an issue you have already reported, please just post a comment in your original thread saying that it still affects 2.4.

Thanks Anto, I'll get this passed over to development. However please understand that it is not as simple as saying it takes 'five minutes' to fix this bug, and that we can copy and paste the working code. The frontend for macOS and Window uses two different programming languages and both use functions unique to that OS.

This is still an issue in 2.3.1 - if you notice in your video Page 3 develops a gap as shown in the Pages thumbnail preview. I also get this behaviour as well in 2.3.1 as well. However I don't understand why you would want to use both 'Keep with previous paragraph' and 'Keep paragraph together' throughout the entire body of text. It is trying to effectively keep all of your text on the same page or frame as all the other text. These options are normally only selectively applied to specific paragraphs to fine tune where you want them to appear. Having all of them options enabled, is just inviting problems and a lot of 'fighting' with the text. Screen Recording 2024-01-18 at 11.16.57 (1).mov

Thanks - It looks like this affects all checkboxes on the Paragraph Panel. I'll get this logged with development.

Thanks! I will pass the report on to development to see if anything obvious appears to be wrong from the hang report.

Just to confirm you have only encountered this hang once and can no longer repeat it?

Is the 2.3.1 you're referring to the current non-Beta version? In which case it is likely that your Text Frame doesn't have all 4 flow options enabled by default (both Retail and Beta apps have different user data). Just to confirm you have only encountered this hang once and can no longer repeat it? It could just be a one off hiccup. I've tried to reproduce by setting my default Text Frame options using your original document as a start and then making new 14 page documents and flowing filler text through multiple linked frames with 2-3 columns. I then repeated that again creating a second document. On document close I get offered to save for both and neither hang when I say decline the save.

Thanks for the report Anto, It looks like it is getting stuck in a loop, and considering the issues you were encountering with all the enabled Text Flow options, I wouldn't be surprised if it was caused by the Text Flow options being applied to every paragraph in both documents causing the loop. Did it happen for you every time (prior to you resetting your Text Flow options)? I'm not encountering it myself, even when I open the document from your other post. How many pages were in both of those untitled documents?

Hi Anto, You've correctly identified the Flow Options - they're all fighting with each other trying to keep every paragraph together creating the oddities you're seeing. Disabling all of these for all paragraphs will solve the issues for you. I suspect at some point (not necessarily with this version) with a beta build you may have saved a text frame default (for example you may have had a frame with a font and size you like so have saved the defaults) with these options enabled, so every time you create a new document it uses that font and size. You can fix this by having highlighting a piece of text and go to Edit > Defaults > Factory Reset and then Edit > Defaults > Save. Every time you create a new document it should now use Arial 12pt, with all flow options disabled (and also reset any other defaults that you may have changed regarding paragraph formatting)

Looking forward to seeing the results of your exports! Curiously what software do you use to import the DXF and DWGs in? I've not done any CNC based stuff myself, but have previously used Inkscape exported DXFs with LaserCut 5.3 at our local hackspace to send to the A0 Laser Cutter. The DXFs we now export now import with LaserCut 5.3 to the correct size.

Hi Debraspicher, I've been around with the Rusty Nibs brush sets but have not been able to make the app crash. Do you remember what exactly it was you were doing when the crash happened? Were the brushes installed manually via an afbrushes or via the My Account dialog. Finally would you be able to go to %UserProfile%\.affinity\Photo\2.0 (Beta)\CrashReports\reports\ and attach the .dmp file that matches the time the app crashed above please? Thank you,

Hi garrettm30, Just to let you know the file was triggering some firewall rules on the forum and this has now been resolved! Hopefully any further images you try should now upload!

Hi Lecho, Would you be able to create a new thread for this issue and attach a video detailing/reproducing the issue you're getting and attach any supporting files (ideally so we can also open them in 2.3.1 to compare) you've used. Thanks!

Hi AP- Thanks for letting us know - I can reproduce that here and will get it passed on to development.

Hi Ronny, What do you mean by New Beta adds increments with 4 decimal places? This shortcut behaviour for [ and ] is intentional. By default [ and ] will change the value relative to what it currently is. This means that the larger the stroke is, the more it will increase. Meaning you can easily just hold the keys down to change it by a large amount relatively quickly if you just want to eyeball things. You can use Shift+[ or ] and it will scale by an absolute amount of 1px for every key press. Arguably this isn't the most useful value for if your line or document is set to something else. This behaviour is not new to 2.4 and hasn't changed from what I can see.

Thanks for the feedback Ronny. We do already have some of these logged, however I will get the others passed onto the UI team for consideration.

Hi Dazmondo77 This is currently working as intended. Layers that were not present when the state is captured are not included or considered when updating the state. You will have to delete and re-add the captured state to then include them. The Update option will only update that visibility of objects already present in the captured state to its current setting.

Thanks for that - I cannot reproduce the issue on a Parallels VM with fresh installs of either Monterey or Ventura, however I can reproduce it on a Parallels VM with a fresh install of Sonoma 14.0, so it certainly looks to be a Sonoma only issue and a regression from 2.3.1.

Hi Paul, Thanks for letting us know I can reproduce this here on 2 machines (both Sonoma without MS Office installed) using both your document and a new document. Both Italic and Bold Italic TNR are being exported out incorrectly as you're seeing - I did a quick try using Arial and that seemed OK. It does look to be a regression in this build so I will get it logged. Which version of macOS are you using? I'll check to see if this is ok on earlier versions of macOS too!

Hi Old Bruce, This is working for me in both 2.3.1 and 2.4.0.2222 using a Full Size Wired British Keyboard also set to British within macOS. What physical layout are you using and what is your macOS set to? HomeKey.mov