anweid Posted November 13, 2019 Share Posted November 13, 2019 The German Affinity Publisher 1.8.0.499 behaves as follows (see video): A text style is used defined with an exact line distance of 15pt (0:00-0:10). Inside the text is an SVG graphics pinned as a character with an offset of 0pt from the base line. If the pin offset is now increased, the SVG moves down, which I find counter-intuitive: It would be more logical if increasing the offset would move the image up. But this is not the main point... The main point is that when increasing the offset to a positive value, the line distance to the next paragraph (which is also defined with an exact height of 15pt) suddenly also increases, which is not intended (0:10-0:19). This already happens if the graphics is still inside the range of the font's descender, which is even more unintended. If the offset is negative (0:19-0:31), the graphics nicely moves upwards without disturbing the line height, which I find wonderful. It would be nicer if changing the offset of a character pin would behave the same for both directions, at least in case of a well-defined line height. Andreas Weidner PinOffset.mp4 Link to comment Share on other sites More sharing options...
anweid Posted November 13, 2019 Author Share Posted November 13, 2019 This also happens in version 1.8.0.502, which I just found... Link to comment Share on other sites More sharing options...
A_B_C Posted November 14, 2019 Share Posted November 14, 2019 Yes, but you can always give the object a negative bottom border, and you can move it down by the same distance without changing he leading. Link to comment Share on other sites More sharing options...
A_B_C Posted November 14, 2019 Share Posted November 14, 2019 Don’t know whether this invalidates your report though. It’s just a workaround … or … whatever. Link to comment Share on other sites More sharing options...
anweid Posted November 15, 2019 Author Share Posted November 15, 2019 Ah, that's a good idea - thanks. I still think that the mentioned behaviour is a bug, but at least this workaround helps me to continue writing for the moment. Andreas Weidner A_B_C 1 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