Quote:
Originally Posted by ghmerrill
But my situation is one where I don't want to stop book development and devote excessive time to that exercise. I'm sure you understand.
|
I understand perfectly.
Quote:
Originally Posted by ghmerrill
The report function is very convenient for me (largely because it gives me a word count), but it's not essential. Unless, of course, this turns out to be a symptom of a more fundamental error, either in the book files themselves (undiagnosed other than by Reports crashing) or in some part of Sigil code outside of Reports. It does look like something's throwing an exception and it's just not being caught at an informative place.
|
There's been a lot of "crashy" stuff reported/fixed with the Reports feature lately, but it's usually been the result of one of the underlying documents being altered while the Reports dialog is still open (and subsequently refreshed).
Quote:
Originally Posted by ghmerrill
I'll put a day into attempting to isolate the problem. (I've got about 30 years of software design/development behind me, and if there's a simple test case to be found, I should be able to find it in that time.) I also have a slightly earlier version that doesn't exhibit the problem, but I suspect that's of little value.
|
Anything you can provide would be helpful. And if it takes longer than a day, then it takes longer.
