View Single Post
Old 12-14-2016, 08:22 AM   #15
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,743
Karma: 206739468
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by kovidgoyal View Post
Haven't seen that myself -- one thing that comes to mind is if Sigil calls show/setVisible on some tabs explicitly, that might mess with the order.
That's a possibility. There's a lot of residual "workaround" code still in place for dealing with maximized window-state issues in Qt4.8. I've no idea if they're necessary or even relevant anymore.

Of the four Sigil dockwidgets that are tabbable, there definitely seems to be a very specific "pecking order" they honor whenever user-tabified dockwidgets are restored. That pecking order should probably be a pretty-good clue as to what's going on.

Thanks for the verification that "current tab" SHOULD be being restored, though. I couldn't find any hard-and-fast evidence in the documentation that that was indeed the case (though it makes sense that it should be). Knowing it should work is half the battle most times.
DiapDealer is online now   Reply With Quote