DesignStationYT

Ah-ha! You're right that it's related to baseline grid, but the grid is being ignored by the table content styles... mostly. It's not aligning to the grid (as intended), but the alignment of the table cell content doesn't work unless the overall baseline grid in the document is turned off. So it looks like the issue is related to some change to how the baseline grid functions in this latest beta?

Since the latest update, vertical alignment in table cells doesn't seem to work anymore, with everything now top aligned. Selecting any other vertical alignment doesn't seem to produce any change.

While a lot of the text in this report is using the baseline, that text has a style applied with Align to Baseline Grid turned off. I confirmed this both in the style itself and in the Paragraph Studio Palette. That's why it's particularly strange that if you do justify vertically the first line jumps to the baseline grid. I should add that this behaviour only just cropped up—it wasn't present before I downloaded the latest Publisher beta.

Hi there, Latest version introduces a baseline grid issue when combined with Justify Vertically. I have a two column text frame that has text which is not supposed to align to baseline grid, but when I do justify vertically the first line tries to align to baseline grid (even though it's not supposed to) and ends up with a strange overlap. Here's a screenshot...

Doesn't affect the outcome — doesn't work either way in Publisher (and as a side note, works with or without a space in Designer).

One last update! I've figured it out. Typing in the unit causes the calculation not to work. In other words, if you have an object at 5 in and you type in +.115 in that will not work. But if you just put in +.115 it will. This isn't the expected behaviour for me, especially as you can type in the unit in Affinity Designer and it'll properly perform the calculation (and it's nice sometimes to have a document in one format—inches, for example—but then do a calculation when you add or remove millimetres or other to an object's size or position).

Hey everyone... Further to this, it looks like it's an intermittent issue (if that). It was driving me crazy on the day that I posted, and had been happening a few days prior too. But since a reboot and relaunching the app, it's been working fine... knock on wood. I'll update again if it crops up again, but hopefully it doesn't.

Since the most recent version (1.7.0.305), I've noticed that I'm no longer able to do additions/other calculations in the Transform studio panel using the number row on my keyboard (typing in [whatever the point position is] + 0.25in and then hitting return just clears the entered calculation), but it still works from the number keypad. Has anyone else run into this issue? Update: actually, I take that back! I'm not able to get it to work from the keypad either right now.

Confirming that this is fixed in 1.7.0.270. Nice work, and thank you!

Will do. Than you!

Document is in rough shape right now and I'm on deadline to wrap it up... but here's a video where you can see the issue in action. Text_Frame.mov

Yep! PDF result and settings attached here.

Not overlapping in my case. Clicking on the frame in the Layers palette is fine, but the moment you go to double-click on a word or select a paragraph a different frame will often suddenly become the selected frame.

Same here! Pretty frustrating when you're trying to select a paragraph in one text box and it seems to really want me to edit a neighbouring text box instead. I've had this happen between pages as well, and only since 1.7.0.257.

I've stripped the file down to just the affected page. Weirdly, I was able to output the PDF without any image issues with previous beta (K only, no appearance glitches), but the most recent 1.7.0.257 now outputs the image as it appears in the screenshot above. K_Issue.zip