Old Bruce Posted November 16, 2021 Posted November 16, 2021 When using the Edit Detached I notice that the bounding box for items (and indeed the entire spread) will shift up or down several pixels. Change the zoom factor and everything is redrawn and so appears fine again. I think this is a result of the big orange bar being drawn on the top of the window. The Spread gets redrawn and the bounding boxes no longer match up to the displayed content. Pretty sure it is a Metal problem, Open GL doesn't have this problem. Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
Staff Pauls Posted November 17, 2021 Staff Posted November 17, 2021 Added the report to the issue -Thanks Bruce!
Petr Stanicek Posted June 29, 2022 Posted June 29, 2022 This problem still persists. I'm creating a book with tons of text frames and this is very annoying.
Sam Neil Posted July 1, 2022 Posted July 1, 2022 Funny I had this yesterday on Windows but I cannot recreate it for the life of me and did find it odd.
Petr Stanicek Posted July 3, 2022 Posted July 3, 2022 No no no, I'm done, this is absolutely insane. If I edit a text frame, everything is deformed and moved, if I finish, the same deformation happens. I have to scroll the page a bit to fix the view (see the attached video). My book has a complex layout and I have to edit this a hundred times per hour, and I'm going mad of that… Plus many other bugs… The same thing as with AfPhoto. I hated to do that, but I had to buy Photoshop – and now I have to buy InDesing to finish my book. Affinity Publisher is not suitable for a serious work. Screen Recording 2022-07-03 at 4.41.36.mov
Customer Feedback Posted July 7, 2022 Posted July 7, 2022 We have also experienced this. There are three things about it that are very worrying from the point of view of a professional user: The functionality (the banner) is extremely poorly implemented. That in itself is worrying, but the fact that the developers themselves have not noticed it, or understood that it is unacceptable, is very worrying. It is very worrying that the poor implementation and faulty rendering of the page is not discovered by a quality assurance team or stakeholders (if any are involved internally) in the testing phase before release to customers. It does not bode well that such a small bug has not been fixed long ago. And remember to always consider major use scenarios when assessing (Serif) criticality. As for example @Petr Stanicek has discovered. A small bug becomes a big problem if it influences a workflow you repeat many, many times. It's very simple. And very destructive. /Eddie
Recommended Posts