Vertical pin position doesn't use real line height

[anweid]

The German Affinity Publisher 1.7.3.481 (Windows) behaves as follows (see video):

1. In the attached document, an image is pinned as a character, automatically increasing the line height, so that the full image is displayed. Fine.
2. Now I want to pin a legend to this image, with the top of the legend at the same height as the top of the image. Unfortunately, this does not seem to be possible with any of the presets...
3. Outside below and Inside bottom are both OK, but all other presets move the legend to a position that apparently does not take into account the real line height (=the image height), but only the text height.
4. Of course it's possible to manually adjust the position by the required millimeters, but this would need readjusting in case of changing image dimensions.

It would be much nicer if Outside above, Inside top and Inside center would use the real line height.

Andreas Weidner

PinPosition.afpub

[Patrick Connor]

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.