Technically yes, but a bit too slowly for me and with too many steps and disconnects.
Having to keep on pressing Update to get it to swap, even though Previews are already cached, seems an unnecessary step. Is there any reason why someone would switch from say, Standard to Lines and not want the image to change to the correct Preview for that?
If there is no Preview yet, then OK, it can’t show it, but if there is: why not show it?
There are also disconnects between Preferences and the Previews. Changing from say Low to High RAM does not force an update to occur, making it impossible to compare results between GPU, CPU, w/ High, Med, or Low without exporting them.
Changing the Noise/Blur sliders does not change the image, although the Preview still says ‘Preview Updated’ with the green bar at the bottom, although the Update Preview button then becomes ‘available’. The image is not changed. Making a New Preview with Noise=0 and Noise = 100 allows you to Press the Update Preview button and toggle between them like different images, but only by doing that.
There have also been times where no matter what I do, nothing changes and I’m forced to move the Window slightly to get it to realise it really does have to Update the image.
In coding terms, this seems to suggest there are several places where the cache is not being marked as ‘dirty’ and there isn’t a full set of inter-dependencies mapped out for each possible change we can make with sliders/buttons.
Even then, sometimes if I move the window only a few pixels to ‘nudge’ it into doing an Update, it still doesn’t light up the ‘Update Preview’ button; which seems to indicate its Preview image is perhaps slightly larger than what is displayed, and if you move the window anywhere within that image (say it has a 5% margin stored?) it considers it the same image and ‘saves time’ by not updating anything.
I also mentioned a few other examples at the end of the v5.5.2 release thread last week that still apply.