Quote:
Originally Posted by quocsan
Dear DiapDealer,
Version 2.2.0 on MacBook Air M2 (macOS 15 Sequoia Beta) does not save state of toolbar items.
|
Can you please be more specific. What "state" is not being preserved? I just tested and I can move and hide various toolbars and they stay like that when Sigil is next launched.
Please attach a couple of screenshots showing the issue as it would help show the problem.
That said, Sigil only saves its state on close and so if you have two main windows open in the same Sigil app (something that can only happen in Sigil on MacOS) and hide clips in one but close it first, the one you close second will be the one whose state is saved. If you quit Sigil when more than one Window is open, it is pot luck as to which state will be remembered depending on the order they actually get the close signal. This has always been the case on MacOS. It will always remember the last closed state.
Also you might want to see if saving the epub, or resizing the Main window has any impact on which toolbars are being shown.
---
As far as I know, macOS Sequoia is in Preview mode only and only introduced last week.
And it has introduced Window tiling which can interfere with the any app controlling its own Window layout. As far as I know, Qt 6.6 and even Qt 6.8 are not Sequoia compatible either as Sequoia was only introduced last week. That said, Qt has tested things against their dev branch and seem to think there are no Qt widget issues: see
https://www.qt.io/blog/qt-on-macos-15-sequoia
I am sorry, but there is *no* chance I would ever upgrade to a Preview release of macOS, especially as Mac OS has had numerous bugs of late that are not worked out until 3 or 4 point releases later. My build platforms are always one full macOS release back from the bleeding edge for stability reasons. I only have a single build machine for each variant of MacOS and can not risk running Beta software on either of them.
So my guess is this is a MacOS bug in its Beta, as nothing related to toolbar state was changed in the Sigil code, as Qt version 6.6.2 has had no changes in that area since the 2.1.0 release.
You should probably also report these issues to Apple via your developer account, and file a bug report directly with Qt if you can recreate this issue with any other Qt based software. So that whatever the cause of the issue, it gets addressed quickly.