Yes, that has been already reported as a bug as well.
Sorry, I must have missed that. ![]()
Yes, that has been already reported as a bug as well.
Sorry, I must have missed that. ![]()
Sorry, I must have missed that.
Ah, no worries, I've seen it posted elsewhere, not here. I meant that it was already reported as a bug to the developers. (I may have reported it, in fact. I don't remember…)
macOS Photos Editing extension missing in V3
Looks like we can no longer round trip edit RAW photos in V3 as we can in V2 and V1, surely an oversight? Reported.
Once you clicked "Develop" after editing your raw file you're in the "Pixel" studio. I you select the move tool you then have the options "Develop" and "Replace Image" at the top left, at right of the RAW file filename. Clicking Develop gets you back to the Develop Studio.
Some panels like Stroke (Kontur) have a fixed height, so it's locked "by design" because the resize area applies to the panel below. It seems a bit confusing at first but it follows the internal "app logic". Whether this logic is OK or flawed is debatable, of course…
By the way, my "workaround" is to have at least one resizable panel in each row. So I can temporarily activate it if I need to resize a panel in the row above or below.
Thank you for the answer. This shows how good and important such a forum is. These many little things that do not work or work unusually - as well as the problem of paragraph decoration described here - make me crazy. I wanted to edit a new document in V3 today and switched back to V2 after a few minutes. There are appointments, it has to be fast and you want to concentrate on the work.
So once again thank you very much for the answer and everyone who works here in the forum.
By the way, my "workaround" is to have at least one resizable panel in each row. So I can temporarily activate it if I need to resize a panel in the row above or below.
I just saw that if I let plates float freely, I can also change all sizes.
![]()
Just reported a bug: Affinity crashes when zooming in over 100% with .af files with embedded raw file.
Just reported a bug: Affinity crashes when zooming in over 100% with .af files with embedded raw file.
Just tested on win11 and it froze my system immediately.
Crash when using Super Resolve after Generative Expand. Reproducible. 30-day free trial.
It may have been reported already but I just reported the failure to save default tool settings. At least for clone and inpainting brushes (maybe others?) setting the layer option and brush parameters is not preserved even within the same session. Switch tools and back, they're back to default.
Win 11 Home 24H2 (soon to be 25H2 as I'm getting tired of the popup reminder)
30-day free trial.
???? you confuse me ...
I got a free trial of the Canva AI. I used the generative expand tool. There is a button to push called Super Resolve. If you click that after the AI finishes, the program closes.
100% reproducible bug on my MacOS Sonoma:
If you want to add Master Pages to your existing layout document, make sure the Quick Export panel is closed.
Else crash, at least on my MacOS Sonoma.Steps to reproduce:
- create a new document
- add a master page – no problem
- open the Quick Export panel
- add a second master page, be it via Pages panel or from the Document→Pages menu
- upon confirming the Master Page dialog: crash
Bug report submitted already.
Can anyone confirm on different configurations?
Hi all,
I can confirm this issue above (by loukash) and have another one:
the settings pop-ups right beside the pixel size fields in the batch job panel are empty:
![]()
Can anyone confirm this?
Best regards
Following the steps above I don't have any crash on MacOS 26.1 even without closing the quick export panel.
Following the steps above I don't have any crash on MacOS 26.1 even without closing the quick export panel.
Same thing for me on MacOs 12.
... the settings pop-ups right beside the pixel size fields in the batch job panel are empty: ...
Can anyone confirm this?
Everything is fine here (Windows 11).
the settings pop-ups right beside the pixel size fields in the batch job panel are empty:
Can anyone confirm this?
This works OK on my Mac, except the fly-out is very tall, about 2/3 of the height of my 27" iMac screen, with a lot of wasted empty space at the top & bottom. I reported it in-app via Ask > Report a bug.
It is likely different for Windows so you should probably report that in the same way.
Don’t have an account yet? Register yourself now and be a part of our community!