Inspector layout lost on every project reload and not restored with Layouts

Is there an update on the status of this ‘Inspector opening default Synopsis/Notes’ allocation?
Regardless how the space is allocated in the sidebar when the file is closed (typically approx. 20/80%), its next opening is for me ~ 80/20%.

Of course, it’s ‘not a big deal’, easily adjusted, but still, I do wince every time I go to the Inspector’s Synopsis/Notes sidebar for the first time in a Scriv3 (Win) session.

:face_with_raised_eyebrow:

(used a translator)

If the language is set to English, the snapshot date table displays all dates

However, if the language is set to Korean, the snapshot date table does not display all of its contents

So I resized the table to show the contents of all the dates,

but when I re-run the program, Scrivener initializes the date table size.

To solve this problem, if I resize the snapshot date table, please add the option to remember the resized size to the scrivener.

1 Like

Thanks, I’ve added few additional notes to the bug report for this. I don’t think it was mentioned that these columns should have a remembered width. I also added that the sort column should be remembered.

1 Like

AmberV, please excuse me if I missed this: It seems to me that before my v3 update to 1.3 (x64), the Inspector Synopsis/Notes balance on program startup was substantially toward Notes (~ 80%, as I wrote above in this thread, Jan 2023).
Since then sometime however, the session-initial balance seems significantly shifted toward Synopsis (~ 90%?), even when there is no Synopsis text and the Notes are substantial; and regardless how I set the allocation in the Inspector during a session (typically, ~ 20/80), when I next open the program, the Inspector’s balance resets to 90/10%, Synopsis/Notes.
Is there switch that I need to set?

Win 11 x64; i7, 32GB 2T (SSS, loath to say ‘drive’)

I don’t know if I mentioned it specifically in thread, but yeah, the weird massive synopsis card default is definitely on that list of inspector layout errors I referred to. I’ve never quite seen it as bad as you describe, but that’s the kind of thing that should never be encountered anyway if it worked right:

  • New blank project uses 5x3 ratio.
  • Whenever you move the splitter in a project it stays that size until the end of the universe (or the last copy of your project that still exists anyway).
  • And as such project templates carry that preference forward too.
  • The split itself should not be elastic when resizing the window height. The card should stay the same size always (until hitting minimum constraints and then it would collapse).
1 Like