Column Rules Missing

[R C-R]

3 hours ago, Murfee said:

The upper text frame has not been resized, it is exactly as I drew it out, the rule extends to the bottom of the inset.

But it does not extend to the top & bottom of the text frame, which is the issue I was considering. With the column rule top & bottom gap size set to zero, I think it should, just as it does when the text frame top & bottom insets are set to zero. Otherwise, to get a zero width gap with non-zero inset values, the top & bottom gap sizes would have to be set to negative values, but they will not accept negative numbers.

 

4 hours ago, Murfee said:

I duplicated this layer and moved it down to line up below the original, I then stretched it down just a small amount to increase the height, I did not change anything else. You can now see that the rule has moved down a small amount in relation to the frame height change. 

I think we are both seeing different aspects of the same issue: the length of the Column Rules stroke should always be based on the height of the text frame, whether or not there are any column insets or rule gaps. That way the gap sizes would remain constant regardless of any frame or inset height changes.

[Patrick Connor]

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.