smadell Posted July 30, 2019 Share Posted July 30, 2019 I rarely use the Shadows and Highlights filter, and had not tried this when a previous beta build announced the availability of version 1.6 and version 1.7 methods. But, for some reason, I gave it a try today. I routinely use the Dark interface, in Separated mode, on a Mac. That having been said, I was surprised to see that the Shadows & Highlights… choice gave me an unusable panel. The background of the panel remains in "Light" interface mode, while everything else is in "Dark" mode. This renders the text unreadable. Switching to Light mode corrected the problems, but this ought to be a fairly easy fix, and one that should be made before RC1 becomes GM. Switching to non-Separated mode didn't change anything. This is a new bug with the v1.7.2 betas - it is not present in the MAS version of 1.7.1. Affinity Photo 2, Affinity Publisher 2, Affinity Designer 2 (latest retail versions) - desktop & iPad Culling - FastRawViewer; Raw Developer - Capture One Pro; Asset Management - Photo Supreme Mac Studio with M2 Max (2023}; 64 GB RAM; macOS 13 (Ventura); Mac Studio Display - iPad Air 4th Gen; iPadOS 17 Link to comment Share on other sites More sharing options...
smadell Posted July 30, 2019 Author Share Posted July 30, 2019 Some more strangeness. I tried the LIVE Shadows and Highlights filter in 1.7.2.149 (also in Dark, Separated mode) and got this (see below) There is extra space on the right, for no particular purpose that I can see. Affinity Photo 2, Affinity Publisher 2, Affinity Designer 2 (latest retail versions) - desktop & iPad Culling - FastRawViewer; Raw Developer - Capture One Pro; Asset Management - Photo Supreme Mac Studio with M2 Max (2023}; 64 GB RAM; macOS 13 (Ventura); Mac Studio Display - iPad Air 4th Gen; iPadOS 17 Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted April 17, 2020 Staff Share Posted April 17, 2020 Sorry. Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum. Report a Bug in Affinity Designer Report a Bug in Affinity Photo Report a Bug in Affinity Publisher Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem. This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build. Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
Recommended Posts