I don’t think this is related to : Bug in tables
Since this seems to be a newer thing than 20 years ago.
Anyway, I’m the author of this post:
which is relatively popular. And for that I created a bunch of tables. The problem is the latest version of Scrivener has a bug in tables which is better demonstrated in how it stores it in snapshots:
On the LEFT is how it’s supposed to store it. And is pretty much how I have it stored in templates. On the RIGHT, you can see it stores it in Snapshots incorrectly.
Thus if the computer crashes, which it does from time to time, it relies on the snapshot on the RIGHT and then the whole table settings are messed up. This is then hours of work to fix.
I can half fix it by putting a space in the empty cells, but then that is a pain because you have to remember to delete the space every time one uses the template. I’d rather the bug be fixed. Something like empty cells does not mean null in snapshot mode.
If every single last template I made with tables (which is a lot) is broken every time I create a file from that template, it’s not fun to use anymore.
Can you please fix it? It might be low priority, but it’s high on the annoyance scale for me. Almost all of the templates I make rely and store as a table (It’s because the left item is bold, but Scrivener won’t remember after creating a file from a template on the right is not bold). I save to snapshots as a “proof of copyright” type of deal.
This wasn’t an issue in previous versions, because I spent a long time doing extensive testing on the templates before releasing them. So I think it’s a newer bug.