Fritz_H

Open any image in Photo 2.4.1 select the crop-tool press the backspace key the image-layer is deleted (why? makes no sense in this context) press ctrl-Z (undo) -> no effect press esc to cancel the crop tool -> no effect (Usability?) click cancel-button to quit crop tool NOW you can UNDO the layer-deletion Although I can almost hear the voice of Serif telling me, that this behavior is intentional.. to me its just one more usability-flaw... one of far to many...

Photo 2.4 on Windows 10 * Open 2 images in Photo * add any adjustment which offers a picker * click the picker-button * switch to the 2nd image / document-tab. * switch back to the 1st image. -> the adjustment floater(?) panel? is gone (invisible), but the picker is still active.

Sorry, not true. I use german Windows-settings and a german keyboard (which of course has a comma printed on the key on the numpad). All 3 Affinity-applications correctly display a comma when I press the comma-key on the numpad. (Google Search, Cherry Keyboard)

Welcome to the world of Serif - the zoo for usability-issues.

perhaps it´s that easy? As we can see here, Windows uses a similar font-size but (far) bigger line-spacing. Windows-Apps use bigger fonts AND even more line-spacing...

Die meisten Computer-Benutzer haben so wenig Ahnung, dass es ihnen total egal ist, wo eine Software installiert ist. Nach (zu) vielen Jahren im Support kann ich das ohne Zweifel behaupten. Es ist nicht sinnvoll über das "was bisher geschah" zu elaborieren - irgendwas ist möglicherweise schief gelaufen. Wenn du die Installation(en) komplett entfernst und den "guten" Installer verwendest um die Software neu zu installieren, wirst du vermutlich so wie ich und viele andere, keine Probleme haben. Wichtig: Hände weg vom "Store"-Installer (MSIX). Das Problem hast du schon in einem anderen Posting angemerkt und eine (wie ich finde) dämliche Lösung angeboten bekommen (komplette Windows-Anzeige vergrößern..) und auch eine Antwort von Serif "Wir sehen es nicht als unseren Fehler wenn nur unsere Software für die User schlecht lesbar ist." Ich bin weiterhin der Meinung, dass Serif hier am Zug ist. Das ist wieder ein anderes Thema über das auch Andere schon viele Postings geschrieben haben ohne dass Serif zur Vernunft gekommen wäre. (Usability Analyse?) Vielleicht erwarten wir zu viel von einer jungen (?) Firma die zB. auch in Version 2.x keine korrekten Lineale liefert. Serif investiert seine Manpower leider lieber in Funktionen für Randgruppen (Astro-Fotografie, OpenColorIO, Normals...). Ich schlage vor, die Diskussion hier zu beenden.

But you are aware, that all those people who complain about the too small interface elements (Fonts, Icons..) are NOT having this "too small"-issue with other applications they use on their computers? only the Affinity-Apps cause issues?... doesn´t that make you wonder?

It´s not good usability to tell the user to do a work-around. Good Usability is: "it works as expected".

@Schölu Falls du es überlesen / nicht verstanden hast: es gibt 2 Arten diese Software zu installieren: - die Microsoft Store - Methode (Softwarename.MSIX) - die "normale" Methode (Softwarename.EXE) Die Arten unterscheiden sich insofern, als die "Store"-Methode dir keine Wahl lässt- gedacht als "sichere" Variante für Leute die keine Ahnung von Computern haben. Ursprünglich hatte Serif mit Version 2.0 nur noch die Store-Pakete angeboten und dafür viel Kritik bekommen. Erst mit 2.1 (?) wurde endlich auch ein "normaler" Installer angeboten (Ich vermute Microsoft erpresst die Hersteller primär die m.E. minderwertigen "Store-Installer" anzubieten.) Ich weiß nicht, ob du den Fehler gemacht hast, die Software im MS-Store zu kaufen und ob ggf. diese Lizenz auch für den "normalen" Installer gilt. Hier der Download für beide Versionen: Affinity Photo 2 Updates (Windows) (serif.com)

Die Affinity-Produkte sind voll mit Usability-Fehlern. Der Hersteller weigert sich diese zu beheben. Ebenso wie Basis-Funktionen nicht repariert oder eingebaut werden. (korrekte Lineale in 10er Unterteilungen? variable Fonts? etc..) Der Vorschlag von @Andreas CH vergrößert ALLES auf deiner Windows-Oberfläche und ist somit nur dann ratsam wenn du auch in anderen Programmen das Problem von zu kleiner Schrift hast. Den meisten Postings hier zufolge ist das aber überlicherweise nicht der Fall, sondern nur die Affinity-Produkte haben zu kleine Interface-Elemente und -Schriften. Da dieses Problem auf der von Serif bevorzugten Plattform (Apple) nicht auftritt, hat Serif wohl kein Interesse oder keine Manpower (oder beides?) um das Problem zu lösen. ------------------------------------------------------------------------------------------ The Affinity products are full of usability errors. The manufacturer refuses to fix them. Just as basic functions are not repaired or implemented. (correct rulers in subdivisions of 10? variable fonts? etc..) The suggestion from @Andreas CH enlarges EVERYTHING on your Windows interface and is therefore only advisable if you also have the problem of too small fonts in other programs. According to most postings here, however, this is usually not the case, but only the Affinity products have interface elements and fonts that are too small. Since this problem does not occur on Serif's preferred platform (Apple), Serif probably has no interest or manpower (or both?) to solve the problem.

Here they are. (did not understand the Zip-Thing, now I do...) Pics.zip

Files attached.

Hi, - when creating a stack the image orientation is not recognized. (stack is shown upside down, when opened seperately the images are shown correctly, pics taken with Galaxy S20+) - issues of the stacking-method selector (?): - when clicking on the "X"-icon a menu pops up ("mean", "median".. )- it does react to the mouse-scrollwheel, but grabbing the scroll bar with left-click results in moving the stack-layer instead of moving the list. - as soon as this happened, the pop up menu is "stuck" - you can move the application window around - the popup menu stays in place. Left-click makes the menu disappear. (Windows 10-22H2 Pro, German-Austria)

In the "Tone Mapping" Persona: at none of the sliders the "double click to reset" feature does work - it does work in other personas. (Photo 2.2.1 set to german on Windows 10 pro (German-Austria)

I'm curious if Serif-support will offer the standard answer: "this problem does not occur on my Mac..."

@Serif: finally bring backwards-compatibility! at least within the same major version. (no discussion please: this IS possible by e.g. using XML for metadata: XML-tags, elements or attributes which are unknown to the old version are simply skipped/ignored - still better than losing the whole work.

About 1 hour ago I sorted the posting in this forum by creation date. Then I counted how many of them are about usibility-issues/requests/complaints vs how many are about feature-requests. Result: exactly 50:50 -> The Affinity-Products suffer from Usability-flaws and -issues but Serif refuses to address them. Instead of fixing these issues, Serif made it even worse. small example: GUI (Top: V1, Bottom V2)

For a short time I was tempted to purchase the upgrade from 1.x to 2.1. but having seen all those complaints about very very basic features being broken or still missing completely: nope, sorry. I am not asking for AI-stuff but basics like variable fonts support or an option to set the color of every guide - perhaps even an algorithm that automatically finds a color that differs from all/most colors the guide crosses on the screen..? Actually I am not asking for any new features but having the UI completely redesigned to meet state of the art usability requirements. But as it seems, the Brits will prefer to add some more "nobody asked for"-filters. sad story.

Dark-grey user-interface elements (buttons) on a very-dark grey background...? Will Serif ever learn about usability?

Sorry, wrong answer / wrong approach. the right answer = the one we expect: "..it WILL be implemented in the NEAR future...." Serif: please forget about fancy filter we don´t need - add the basics finally. (..variable fonts?)

Trying hard to disagree at any cost, hm? I pointed out clearly that incompatibility is NOT common, it can easily be addressed by the developer and even a "save as <old version>" is common practice. None of that is provided by Serif. I can not think of any reason why a customer like you does intentionally disagree to a relevant feature and useful improvement for all those victims of Serif who lost many hours of work due to Bugs in pre-Beta Software sold as "V2.0".

What's the difference between Microsoft 365 and Office 2021? - Microsoft Support For some unknown reason, you keep talking about the different license-models. That´s not the point here...

Office 365 is more or less the same as Office 2019. (which is not fully true since Office 365 receives new features every now and then.. recently they added a writing-style-optimizer etc..) Office 2016 and older are different products with a different feature set. 2007? really? we discuss incompatibility from V(n) to V(n+1). Office 2007 is 3 or 4 Releases ago (2010, 2013, 2016, 2019) since we are now at Office 2021.

In these cases: 1. the updates are free 2. the updates provided an improvement over the previous version. both is not the case when comparing V1.x vs V2.x Compatibility depends on the data-structure in the file. Microsoft uses (some type of) XML. Feature A Option A.1 Parameter x Parameter y Option A.2 sub-option A.2.1 Parameter x Parameter y etc. etc. Features that are unknown to the old software are simply skipped. That way lots of contents may be preserved. useful since: 1. usually only some of the new features are used in a document (80:20-Rule 80% of users use only 20% of the available feature-set) 2. Serif did not add that many new basic features to V2.0 Google offered me this: How to Save a PSD File for Older Versions of Photoshop (lifewire.com) "When you open a newer Photoshop PSD file in an older Photoshop version, the new features of Photoshop don't carry over when the file is opened in a version that doesn't contain these features." There is no reason why a V 2.x file which contains only V1.x-features (an image, a text-box and perhaps a Gaussian-Blur live-filter) can not be opened by V1.x Of course: if the V2.x file contains the (for most) useless normal-map stuff, this will be lost/skipped when opened in V1.x I think, Serif made this incompatibility intentionally since it is possible and common: I already mentioned MS Word. Other major developers offer at least to save to older formats: Drawing file format compatibility in AutoCAD | AutoCAD | Autodesk Knowledge Network (Btw: there is a new AutoCAD-Version every year = file-compatibility is given in chunks of multiple releases.. => AutoCAD 2018, 2019, 2020, 2021, 2022 and 2023 share the same, compatible file-format...)

Serif-FAQ: "As you would expect, V1 will not be able to open V2 documents,.." wrong. I expect that V(n-1) does open files from V(n). Ever heard of a software called Microsoft Word? Guess what: Files created with Word 365 can be opened with Word 2019, 2016, 2013, 2010, and 2007. Features that are not available in an earlier version are ignored but the document and most of it´s contents are available. Please: no discussion about "this is not possible..." it simply is possible; Serif just did not implement it. Lack of time? Lack of knowledge? attempt to force customers to fully migrate to V2.0? We don´t know...