R C-R

Layer menu > New Live Filter Layer > Blur > Diffuse Glow.

The only thing I can suggest -- but it is just to see if there might be something other than Affinity involved & not itself a fix -- is to select an Affinity or other graphics file in Finder, open the Get Info window & tick the "Hide extension" box. If the Finder 'show all' pref is disabled, then the extension should disappear immediately, both in the Get Info & Finder windows. If that doesn't happen then whatever is causing your issue must have some other cause.

I wondered about that too but apparently "Hokey Pokey" is the North American version of "Hokey Cokey." Either way, it is a hokey explanation! 😁

I don't know if the adjustment not working as a child layer is a bug, by design, or what, but the only way I have found for the adjustment just to apply to the layer immediately below it is to use the "Merge" button in the adjustment window to destructively 'bake' the transparency into it, if that makes any sense. Maybe someone else has a better way to do that.

As explained here, if Finder Preferences > Advanced > Show all filename extensions is enabled, this causes all file extensions to be shown, even if the 'hide extension' flag is set for any of them. So if you want the "Automatically Hide Extensions" option in Affinity to work, that Finder preference must not be enabled. Also, I don't know if this is something specific to my iMac running Mojave or what, but I normally run with the Finder 'show all' option enabled & the "Automatically Hide Extensions" option in all the Affinity apps disabled (so all file extensions are always visible everywhere). In testing, when I first disabled the Finder option & then enabled the Affinity one, it had no effect, but after quitting & relaunching the Affinity app it did. So it may be necessary for you to do the same quit & relaunch thing for it to work in your Affinity apps, but maybe not.

Thanks. I never would have known about the bug because "Metal compute acceleration" is not available on my old iMac.

@walt.farrell beat me to it!

Try this: Make sure you have a "(Pixel)" layer selected Select the Blur Brush Tool Select a simple round brush preset from the Brushes panel (Optional) Set the brush width to a largish value, say 10% of the document width On the context toolbar click the "More" button Set the Spacing slider all the way to the left (to 1%) & the Flow slider all the way to the right (to 100%) Make sure Blend Mode & Wet Edges are set to 'don't set' Drag the brush over any part of your pixel layer that has at least some detail You should see a very strong blur effect.

Are you sure your RGB document has some variation in its alpha transparency like in the first Gimp screenshot? When it does, as in this simple Alpha curve adjustment.afphoto example, I get results very similar to those you get in Gimp.

Wow! At least for me reducing the Spacing to the minimum 1% makes a huge difference in the amount of blur the Blur Brush applies in one stroke.

In the iPad version "Projects" are functionally equivalent to folders, so from the New view you can create project folders, name them however you want, & then in the gallery view drag individual documents into them. To remove a document from a project, use the hamburger menu for that item. BTW, there is a separate forum for the Affinity iPad versions here.

OK, that at least seems plausible ... if "Last Week" really means "Posted in the last week, not including yesterday & today, which are listed in their own sections." But as just now, I also occasionally get things like this with 2 "Todays," one of which appears before the "Yesterday" list.

Thanks. That seems to work.

What do you suggest?

Be that as it may, vector objects like those AD & many other apps can create are inherently resolution independent, meaning they are based on geometric descriptions, not pixel maps. This makes it possible to scale them to any size or rotate them to any angle without becoming blurry or pixelated (as long as they remain vectors). This includes dimensions & positions that are tiny fractions of a pixel. So for example, consider this tiny vector shape shown at 1500 % zoom level against a 1 px grid. Each of its four nodes is perfectly aligned on whole number X/Y coordinates of the pixel grid, yet it would be impossible to map all of it to whole pixel values when exporting it to a raster image file like JPEG or PNG. But what is possible (& why vector shapes are so useful) is to change its size and/or rotate it without it becoming blurry or pixelated, as long at it remains in vector form. simple vector shape.afdesign