Jump to content

Recommended Posts

Posted

I can confirm the behavior you are seeing.  Publisher 1.10.4.1189 on Windows 10.

Some tables behave better than others.  In tables which misbehave, I can sometimes get close to the expected behavior by setting the No Break character property on the cell contents.

I've also noticed that tables which are misbehaving often ignore, or misapply, the cell insets. So the cells are not only too small, but the contents are shifted inside the cell, frequently to the point where they run outside the bounds of the cell altogether.  So I suspect there are several interacting bugs here.

As a more general comment about resizing tables and table columns, I really do not care for the way columns resize proportionally.  A simpler, more predictable, and easier to use UI would allow dragging the right table boundary to resize only the rightmost column, and dragging a column boundary to resize only the column to the left of the boundary, moving (not resizing) all the columns to the right (except possibly the rightmost, which might resize to keep the right table boundary fixed).

Posted

Hi @Ning,

Welcome to the Affinity Forums :)

Many thanks for your report! I've been able to replicate this issue here also, and therefore I'm logging this as a bug with our developers now.

I hope this helps!

Posted
20 hours ago, Dan C said:

Hi @Ning,

Welcome to the Affinity Forums :)

Many thanks for your report! I've been able to replicate this issue here also, and therefore I'm logging this as a bug with our developers now.

I hope this helps!

Thank you for the reply! Hope you guys will fix this soon. 😁

  • 1 month later...
Posted (edited)

Is there an update on this bug? It's been driving me crazy. If this wasn't such an issue, I think I'd be much happier with using tables in Publisher.

That being said, I think I figured out something weird about this. I've been using "No Break" as suggested above, and it seems to help a lot, but it only seems to work sometimes. It seemed like "AutoFit Column to Context" was only "listening" to one row. So, Row 4 had the longest text in Column A, and AutoFit listened to that when applied to Column A. When I try to AutoFit Column B, it seems that AutoFit is still "listening" to Row 4 and AutoFits to that instead of the longer text in Row 3's Column B. Thus, with Row 3 having the longest text again in Column C, AutoFit works fine again for Column C.

Here's the even weirder part: it doesn't always do this. It did this in the original table (that I was actually using), but it didn't do it in the first table that I copied, but then I copied the original table again (and made fewer changes to it) and the problems showed up again!

apub table issue.png

EDIT: I said it doesn't always do that, but I think there are more rules than I noticed. It seems that AutoFit only "listens" to later rows. So, below, in Row 5's Column B, it AutoFits fine even though Row 4's Column A still has the longer text. However, Row 4's Column C is now broken because AutoFit is listening to a later row (Row 5) at that point. So, AutoFit on Column A listens to Row 4, AutoFit on Column B listens to Row 5, but AutoFit on Column C is being weird—it doesn't seem to be listening to anything.

1240038124_apubtableissuepart2.png.fb3ef030038b3030e6eb0fce9e28c2be.png

But it gets weirder! Because "Evenly Distribute Columns" seems to get stuck. If I hit that button (for all of the columns at the same time), then, even if I resize the columns (which I have to do through the Table menu and I can only make them bigger for some reason), then, if I AutoFit, they just Distribute instead.

Edited by greysonwhy
Additional information
Posted

Hi @greysonwhy,

Welcome to the Affinity Forums :)

Unfortunately this issue isn't yet marked as fixed, though I can see some development input internally, so it's certainly being looked at.

I'll be sure to provide the further information in your post to our developers now, many thanks for your report!

  • 1 year later...
Posted

FYI & FWIW
Tables, AutoFit Columns to Contents, still seems broken in AfPub v2.1.0. Until this gets fixed I'm exporting a PDF from the spreadsheet program, LibreOffice Calc.

 

image.png.ba956dbf697ac3e92d2b4981b9629e4a.png

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.