woefi

I noticed this too, several times (– I'm now on macOS 13.6.6, but it has a history back to macOS 12). -> Even worse, sometimes a dialog (save or export – can't remember) comes right out of the layers panel! ...which forces the panel to slide to the side to have enough space around it... I think I have seen enough to use this occasion to kindly ask the dev team: Please reconsider all UI elements regarding the z-positions and also get rid of the "sliding out" save sheets and use proper dialog windows which you can move around. As much as I love the Affinity Suite and its multiOS approach, the lack of love for the native Mac UI is frustrating at times.

I observed a lot of these anomalies, too. My theory is two combined factors: (A) some programmer(s) do not use light mode and therefore simply "forget" that they are working on a light/dark universal UI project so the icons and assets have to be universal/interchangeable and (B) testing is done mostly in dark mode so only we are seeing it. In an ideal workflow, one of the two stages should catch this from shipping, though... (but I also suspect they are the same pair of eyes)

Well, given how the "Figma-situation" went down, I think this is not a realistic scenario...

the statement reads as "nothing changes regarding v2" (pricing , licensing, updates) ...until the next major version (v3?) is released. So, we are maybe one or two years safe?

Joke or scam, but definitely not real.

curious if there is even a difference between your beta (which there were two release candidates) and the actual release version: Could you check the "build number" of them both? (under My Account) release build: 2.4.0.2301 last beta (RC2): 2.4.0.2301 This would mean, it would have to do with other parts of your system, maybe corrupt preferences? Did you also wipe the preferences before reinstalling Photo?

Although this is off topic in this thread, I say I would appreciate this addition...

Ce n'est toujours pas une pipe...

I think, it would be necessary to differentiate what kind of AI you (or the OP) mean: I'm not entirely sure I need an image drawing robot (except maybe a bit of picture extension in AfPhoto when you just need a little bit more room going from landscape to portrait...) But I would really benefit from workflow additions powered by AI, like: finding missing linked images when the image folder was just moved a little in the file system's hierarchy (AfPub) repeating tasks already done several times (working with multipage documents or complex illustrations) and so on... Computers have always been an artificial extension of our drawing hand, and to get work done more efficiently so you can concentrate more on the "creative" side of your work. (I definitely don't want it to hallucinate anything I can dream of by myself)

Or is it? Bildschirmvideo 2023-12-06 um 14.29.mp4

Thanks, Walt! I just realised, I was always "cloning it wrong" because I ALWAYS used <option>, like in my old Illustrator days 🤯. Strangely it always worked, but as you explained it also disables snapping and so you had to release <option> midway and this always felt incorrect. So now that I know to use <CMD>, it was the first time in 5 years of using affinity apps, that I saw it behaving just like <option> did in illlustrator. (mindblown...)

"mind the gap" toolbar 🙃

Wow, thank you! I always looked for this in the "edit colour" box... EDIT COLOUR looks the same as CREATE COLOUR but without the overprint checkbox why would they hide it there?

Absolutely! Normally I would have completely ignored these overprinting colours and would have instead requested adding the missing feature "set object-based overprinting to fill or outline" but... I see the long list of things I want to be added to the Affinity apps (just for feature parity with Adobe CS5 in terms of print production) and then I restrain myself and accept that it will take them a little bit more time to get there... (I am very confident, though, as the Affinity team is at least very transparent what they are currently doing.)

What is still not possible, yet: To set/unset a colour to overprint _after_ it was created.

I too, would like to see better support for macOS's QuickLook Preview function. Maybe it shouldn't be a pixel preview but instead a crude, lowres, PDF version? Whatever is technically possible... I'm not sure I know any such examples (as I don't use modern adobe apps for comparison). Anyways, here is a link to Apple's developer documentation: https://developer.apple.com/documentation/quicklook

I think this is not a bug per se, it's just "as designed" at this point... But, I too, want the app to: A) preset a custom colour palette, the app should start a new document with (and pre-define it in the templates) B) have the app prioritize an existing document palette (which was saved in the AfDesigner/AfPub file) Use cases would be: (A) Starting a new screen design (Banner/Website/Icon) it uses MY predefined palette of (global)RGB colours, maybe called, say "Webdesign RGB". (A) Next, when creating a business card for my client XY, I choose the corresponding template and change the colour palette to my predefined "Client (XY) CMYK" (B) And every time I re-open these documents, the right palette in the swatches panel is already pre-selected so I can work right away.

Good catch! My old Acrobat Pro (v9) does not display this info Can you repeat this with AfPublisher if you have it installed? I'm beginning to think it may indeed a localisation bug (german) in AfDes but is linked to the system language not necessarily the program language.

I would like all to be specific in which program the error occurs. I'm still having issues in Designer. Publisher is now (mostly) fine. So Yesterday I had to quickly export a Print PDF from a Designer document and the resulting PDF did wrongly include "US Web Coated whatever" instead of the correctly set "Generic CMYK". So when you checked it in Adobe Acrobat you saw that all the colours were cross-converted (0/100/100/10 became 3/96/80/5 or something like that) My Workaround for now is to finish the job in Designer and then open the file in Publisher just to export the PDF for the offset printing firm. (Most of my print jobs are Publisher files anyways... I use AfDesigner mostly for logos and info-graphics, which I then link in AfPub)

eventuell: Mischmodus: Multiplizieren? weiß multipliziert nicht...

@Johannes FYI: I think I found some sort of fix: (your video shows the english version but your name suggests that you may be german speaking?) Prerequisites: This was not a fresh install and I had several betas installed this year (I think it has to do with the preferences) I had my language set to "Standard" which is "german" in my operating system. I had the same problems like you showed in your video I changed my program language to "english" and restarted the app -> some things improved I changed it to "german" and restarted the app I changed it to "Standard" (which should be german) and restarted. -> Now The list is sorted right and it remembers the right profile in the document*. I repeated this for all three Apps (AfPub AfDes AfPhoto) * -> BUT: I'm still having difficulties with the MAIN program setting for the default CMYK profile: sometimes it works, sometimes it does not stick...

Quite possibly though it seems somewhat odd... THIS!!! If I change my language from "german" to "english" (not US, and there is no United Kingdom either...) then the profile stops reverting in Designer! ...and the list is sorted right – which is an indication that this is somewhat linked.

Next thing I see: Both in Designer AND Publisher if you change the CMYK profile in settings, then it always reverts back to US Web Coated SWOP after closing the app... Man...this gets weirder... I have to downgrade back to 2.1.1, I have real work to do...

To clarify: The bug seems to be in Designer 2.2 mac the ICC-list "Text" does not match the underlying list "objects" the second from above in Publisher corresponds to the second from above in Designer, but is labelled differently to me it started with a project using "ISO Coated v2 300%" right after the update. edit: maybe a localisation bug just for non-english versions? I'm using it in german.

is this Designer or Publisher? (Note: it is working in AfPub, the problem is with Designer)