iBaloo42

Sorry for my answer... That was not very gracious of me. I appreciate that you tried to replicate the issue, but what is happening on one system might not happen on another one. That is why the classic developer's excuse, "it's not a defect, it is working on my machine" does not stand up in a respectable software development environment.

Thank you Ron. It's great that you have sun above your house, but mine is still under dark clouds. AKA, your post is not very helpful.

The brush size/hardness control is not working on Affinity 1.7 by using the Wacom pen (similar to using Alt+Mouse_RC+Mouse_LC). I already reinstalled the Wacom drivers after uninstalling and removing all the settings and registry keys. I have the following configuration: Affinity Photo 1.7.0.367 - latest version Wacom drivers 6.3.34-3 - latest version Windows 10 64 bit on Lenovo Yoga 920 Moreover, Drag+Alt to pick a color is way off, both while using a pen or a mouse; the color picker magnifier shows snapshots from a different area of the image.

Given that the 1.7 beta seems to take forever when will Sherif release an Affinity Photo update for 1.6 Windows containing RAW file support for new cameras?

The macros environment seems to have been implemented to satisfy a marketing checkmark ("yes, we have it"). Unfortunately, by the struggle of the Affinity development team to avoid breaking everything while writing new code (they have a serious quality problem), I would keep my hopes very low when it comes to expecting for new meaningful features...

I don't think that this feature is open for end users, by reading this post. And, no, the Xcode JSON jargon should not leak at all in the GUI. It is OK to describe in the help/documentation that the builders can be extended by end-users by using Xcode JSON, and it should provide proper instruction of how, where these JSON files are stored, etc., but only, and only if the JSON-based extension is open for use by an end-user. Otherwise, the builder should have had just these three options, Apple, OSX, iOS and the help should have explained the expected outcome if any of these three options are selected. This is a rushed hack.

Thank you Walt. On #2: keeping the aspect ratio, when I'm about to export, makes common sense to be the default behavior. On #3: I knew what the help is saying about the "Xcode JSON". However, it is a very un-helpful description; the help is saying to me that "just ignore this, don't worry about this strange thing, it is just a provisionally created for our GUI developers", which is also very unprofessional when it comes to software development as it leaks developer lingo ("Xcode JSON", really????) to end-users. This feature is still just a geeky hack unless becomes better described and open for end-users to define their own "Xcode JSON" based builder extensions.

I might be considered as being mean spirited, but it seems to me that the whole Export persona in Affinity Photo is half baked. 1. Why there is no support in the Slice tool for predefined format factors? You already have nice support for predefined and custom modes in the cropping tool. 2. Is there any help of how the "Size scaling" can be used besides using a multiplier for size? For example, I would like to instruct to fit the slice to a predefined size (1920x1080, 640x480, etc.). Moreover, I would add this option to export with fitting to predefined size in the "Export Presets". 3. What is that Builder thing in the Slice Export Options? The way is implemented now, looks like a hack to some requirements that you might have had.

This issue has been ignored for a long time. It is ridiculous. This was brought up years ago! Make it an option. It takes several hours--if that, and if not, I would be very concerned with your software design practices--for a developer.

This issue has been ignored for a long time. It is ridiculous. This was brought up years ago towards Affinity Photo! Make it an option. It takes several hours--if that, and if not, I would be very concerned with your software design practices--for a developer.

It is not greyed out. I'm using the latest Affinity version on Windows 64bit.

The fact that one filter, or any other feature, does not work, by design, on a certain context is acceptable. The fact that there is no indication that the given feature is not valid in a certain context, is not.

Bilateral Blur is not working on 32 bit HDR format, in the current 1.6.5 version neither in the latest 1.7 beta version.

For now, I am recommending Supreme Photo; it is the only DAM product that supports properly Affinity files. Per Karlsson’s “How I found my best Digital Asset Management (DAM) system” blog posting helped me in my research; I tried most of the products that he mentioned. If Affinity will provide a free “DAM” delivered as part of their Photo, Designer, and/or Publisher products, it will probably end up being a glorified library similarly with what Skylum did in Luminar 3. However, if Affinity chose to implement a real DAM product that would be a viable alternative to Lightroom, they would not be able to give it away for free (as part of Photo, Designer, or/and Publisher) as such product would require costly initial and ongoing effort.