Quote:
Originally Posted by KevinH
Which means that Dialog's destructor was not called until Sigil itself quit. The close event code I added should fix that issue.
|
Confirming that I see the same behaviour as odamizu when I quit/restart with the 397 Windows build. Which I course I didn't see yesterday because I was removing my sigal appdata dir each time I tested to make sure I didn't have any previous configuration problems

.