Point taken, LOL. It can occasionally be useful if something was broken in the retail version and in the latest beta, and you want to check that you weren’t imagining it was fixed in the previous beta and then broken again, but I suppose such things should be left to the developers or QA staff.
< nitpick >
Nitpicking is uncountable, like sunshine, so (in the same way as we never have two sunshines) you can’t have “a nitpicking” rather than just “nitpicking”.
< /nitpick >
Now I see why sometimes on this forum there are pages of discussion for even the most basic things.
What surprises me is not the answer that @Asser82 gave, for what I know he is not necessarily a developer, but the fact that @Mark Ingram agrees.
Asser82, your assumption is wrong. "If something gets updated" is not, in this case, a stable release. What you refer to is the update your browser, in its official release, does automatically.
If I, the user, decide to download and install a beta release, these are the options I get during the installation:
It's totally normal for a user to have multiple betas installed in different locations. In fact, I can install multiple betas in separate folders.
Also, as far as focusing on the real problems, that's an old mantra I've heard here so many times. It's actually the core of Affinity: let's add A, B, C, D then let's focus only on C & D because we don't have time nor resources to cover everything. Yeah, makes a lot of sense, especially when there are users who were lured by A and B!
If they don't have the time to play with secondary features, why waste their time in the first place? Or why, to put it more simply, don't we call this for what it is? A mistake, which can happen to anyone. They customized the installer, they didn't expect a user reaction to it (they followed their idea of how this would work), and now here we are.
Oh, before I forget, to answer your "you can't place it into a new folder", guess what? I went through the process of installing the new beta again, but first, I uninstalled the previous beta, which it is something I don't usually do (basically Affinity updates over the latest beta's path) and, to my surprise, my old beta's folder is now empty (Affinity Photo Customer Beta) and a new folder appeared (Photo Customer Beta). Yes, I left the default options the installer comes with untouched but gives you a glimpse of consistency. Quite a convoluted experience for something so basic.
Following on from a previous post, I've created three sets of macros for selecting a part of an image based on five Blend Ranges 'luminosity' curves (nominally called Blacks, Shadows, Mid-tones, Highlights and Whites).
You can download the zip file here (the forum doesn't seem to like zip files, so I put it on my website).
A few points of note (more in the included .pdf file):
The 'Preview' set just cuts out the selection so you can see exactly what is being selected. It also lets you inspect the Blend Ranges curves.
The 'Select' set turns this into a selection in the image.
The 'Blend' set does the same for adjustments and filters.
Curve overlaps are deliberately symmetrical so together they should sum to 100%.
All sets include all contiguous combinations, such as 'Blacks+Shadows'.
