Possible minor bug in 0.9.x

[Fedwin]

I think I noticed a bug in Sigil 0.9.0 that is still in 0.9.2. Every time I generate a table of contents, a space gets inserted between the opening quote and the s in all instances of class="sigil_not_in_toc".

I just replicated this error in the Sigil User's Guide 0.7.2 with Sigil 0.9.2.

[DiapDealer]

Sure does. And it's cumulative, too! Thanks for the report.

[theducks]

Minor annoyance:
If you stack (on top of each other. you get a tab at the bottom.) the 'book browser' and the TOC, Sigil does not remember which tab was on top (active view) when restarted. IIRC way back when... it did remember

[BetterRed]

Originally Posted by theducks

Minor annoyance:
If you stack (on top of each other. you get a tab at the bottom.) the 'book browser' and the TOC, Sigil does not remember which tab was on top (active view) when restarted. IIRC way back when... it did remember

Similar here - should be fixable because the calibre editor does remember last selected tab - assuming the docking is implemented by Qt.

That said I prefer software that allows user to set a specific 'start state'. I never liked the 'start where ever I happened to be last time' approach, it seems to imply one never finishes anything.

BR

[DiapDealer]

Originally Posted by theducks

Minor annoyance:
If you stack (on top of each other. you get a tab at the bottom.) the 'book browser' and the TOC, Sigil does not remember which tab was on top (active view) when restarted. IIRC way back when... it did remember

If I leave the ToC on top, it remembers that just fine!

[DiapDealer]

Originally Posted by Fedwin

I think I noticed a bug in Sigil 0.9.0 that is still in 0.9.2. Every time I generate a table of contents, a space gets inserted between the opening quote and the s in all instances of class="sigil_not_in_toc".

I just replicated this error in the Sigil User's Guide 0.7.2 with Sigil 0.9.2.

Just pushed a fix to the github repository that I think will address this issue. It will be in the next release. Thanks for reporting it.

[DiapDealer]

Originally Posted by theducks

Minor annoyance:
If you stack (on top of each other. you get a tab at the bottom.) the 'book browser' and the TOC, Sigil does not remember which tab was on top (active view) when restarted. IIRC way back when... it did remember

I know people probably get tired of hearing this, but I really think this one's on Qt.

The state of all widgets is being properly saved/restored (and hasn't been changed recently to my knowledge), but it seems as if Qt5.4.2 is enforcing its own preference regarding the display order of multiple tabbed/nested widgets.

I know this has not always been the case in the past, and hopefully it will be corrected sometime in the future. Because unless I'm missing something, those saveState/restoreState calls can't really be finagled in any way. They are what they are.

[theducks]

Originally Posted by DiapDealer

I know people probably get tired of hearing this, but I really think this one's on Qt.

The state of all widgets is being properly saved/restored (and hasn't been changed recently to my knowledge), but it seems as if Qt5.4.2 is enforcing its own preference regarding the display order of multiple tabbed/nested widgets.

I know this has not always been the case in the past, and hopefully it will be corrected sometime in the future. Because unless I'm missing something, those saveState/restoreState calls can't really be finagled in any way. They are what they are.

I totally understand.
QT is a building block...with flaws. The problem... No competition You get what you get.

for looking