View Single Post
Old 12-30-2019, 09:58 PM   #7
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,841
Karma: 6120478
Join Date: Nov 2009
Device: many
From your ini file it shows that in both cases the Sigil app is Maximized.

Does this crash happen if you do not have Sigil maximized?

KevinH

Quote:
Originally Posted by Turtle91 View Post
I got a new monitor - yay Christmas! - and thought I'd see if Sigil (v1.0.0) still had it's second monitor crashing issue....and yes, it does.

Both monitors are the same model (3840x2160) running on Windows 10 (latest version). I have the desktop extended in the vertical direction - secondary monitor above primary. Although, the crash still occurs whether its extended vertically or horizontally; and it crashes even when I reduce the resolution on both monitors down to 1024x768 (talk about unnatural! ).

The problem happens when I try and instantiate the undocked Preview Pane (PP) on the secondary monitor. This can be done either by:
1 - having Sigil main window on the secondary monitor and then double clicking the PP to undock it

or

2 - closing Sigil with the PP undocked on the secondary monitor - the next time I run Sigil the PP tries to reopen on the secondary monitor

It's important to note that undocking the PP on the primary monitor then moving it to the secondary works just fine - it only crashes when the PP is initialized on the secondary.

Once Sigil crashes the work-around is to delete (or rename) the Sigil.ini file and then Sigil opens with the PP re-docked. However - I went back and did some testing with the .ini file. I copied pieces of the original .ini into the newly generated .ini and tested by opening Sigil. It opened just fine every time. ie, It eventually opened just fine with all the original .ini information.

I've attached my .ini files (created after closing with PP undocked on the primary monitor - which works fine, and another one after closing with PP undocked on the secondary monitor - which crashes) in case that helps. I've also attached an image with the two files compared showing the small changes in the "[mainwindow] toolbars" section.

FYI - I also left the Saved Searches and the Special Character windows open on the secondary monitor when I closed Sigil. Those windows were closed when Sigil restarted, as they should be, so I think this is specific to the PP.

Does anyone have an idea? Is there an .ini setting that tells Sigil to have the PP docked on open??
KevinH is offline   Reply With Quote