jmwellborn Posted February 18, 2020 Posted February 18, 2020 Although I have created a macro which is identical to that demonstrated with the Affinity Photo: Macros tutorial, when I try to use it on an image to which the correct crop/straighten steps have been applied, instead of the macro working as set up with the first step LAYER>Rasterize and Trim, when I click on the macro I get a full canvas of transparency. The image also vanishes from the layers panel. But if I crop and straighten the image, and do the LAYER>Rasterize and Trim step first, then click on the macro, the other three steps work perfectly. What am I doing wrong? Since the macro contains the Rasterize and Trim step, why won't that apply? Also, even in the tutorial, the first step is "Rasterize" rather than Rasterize and trim. @James Ritson could you help??? 24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.7. Photo, Publisher, Designer 1.10.5, and 2.5.5. MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB SSD storage, Ventura 13.6.7. Publisher, Photo, Designer 1.10.5, and 2.1.1. iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil. Wired and bluetooth mice and keyboards.
Staff Patrick Connor Posted April 17, 2020 Staff Posted April 17, 2020 Sorry. Thank you for reporting a problem using 1.7.x . 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 current 1.8.3 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
Recommended Posts