On Sat, Sep 5, 2009 at 6:49 AM, <J.B.C.Engelen@...1578...> wrote:
I agree that end users should not suffer a crash for us to find bugs. However, this exception is a low level check to see if the path is still a valid path.
This late in the release, I'm afraid we have no other choice. Is it crashing? Yes. Can we fix it "properly"? No. Can we fix it at least somehow? Yes, by removing the assert, or at least making it non-crashing. I think the choice is obvious :)
It's like the many other assertions Inkscape contains.
Except that those other asserts stand on guard but never fire, in normal use. This one fires (and kills).
By the way I never had crashes from this assert on Linux, even though I also use Wacom with Calligraphic pen extensively. So this seems to be a Windows-only bug.