Ketarin-1.0.48

Added x64 sqlite.interop

Ketarin-Mono-1.0.47

Updated Linux-behavior.md

Updates are based on research results for issues #37 & #34.

Ketarin-1.0.47

Updated Linux-behavior.md

Updates are based on research results for issues #37 & #34.

Ketarin-Mono-1.0.46

Fixed #55

Changed code to use a regular ListView for Mono instead of
FastObjectListView.  The FastObjectListView doesn't seem to work on
Mono, AFAICT, it never tries to display the information at all, and my
best-guess is that's due to a bug in Mono itself.  None of the special
features of ObjectListView or FastObjectListView are used, so the only
possible advantage is if they are less limited in the number of errors
they can display, than is ListView.  There's a small chance that
ListView will fail (i.e. not display them all) if there are too many
errors, but at that point, I'm not sure the error information will be
useful, since it'll be many thousands of errors (the old limit on
Windows was 32,767, but that was doubled, IIRC in Win2k, XP and later,
and I've no idea what Mono's limit might be).  If the limitation is
causing issues, I'll probably rewrite the dialog completely. :)

Ketarin-1.0.46

Fixed #55

Changed code to use a regular ListView for Mono instead of
FastObjectListView.  The FastObjectListView doesn't seem to work on
Mono, AFAICT, it never tries to display the information at all, and my
best-guess is that's due to a bug in Mono itself.  None of the special
features of ObjectListView or FastObjectListView are used, so the only
possible advantage is if they are less limited in the number of errors
they can display, than is ListView.  There's a small chance that
ListView will fail (i.e. not display them all) if there are too many
errors, but at that point, I'm not sure the error information will be
useful, since it'll be many thousands of errors (the old limit on
Windows was 32,767, but that was doubled, IIRC in Win2k, XP and later,
and I've no idea what Mono's limit might be).  If the limitation is
causing issues, I'll probably rewrite the dialog completely. :)

Ketarin-Mono-1.0.45

Fixed #58

Updated code to not call String.Replace() if we have an empty string for
what to replace.

Ketarin-Mono-1.0.44

Fixed #57

Added code to set this.DialogResult to DialogResult.OK when the OK
button is clicked.  This seems to resolve the problem.

I'm not sure how this was working before, or how it suddenly stopped
working.  This change should guarantee it works as expected (pending any
changes from upstream that may test the result of the dialog
differently).

Ketarin-1.0.45

Fixed #58

Updated code to not call String.Replace() if we have an empty string for
what to replace.

Ketarin-1.0.44

Fixed #57

Added code to set this.DialogResult to DialogResult.OK when the OK
button is clicked.  This seems to resolve the problem.

I'm not sure how this was working before, or how it suddenly stopped
working.  This change should guarantee it works as expected (pending any
changes from upstream that may test the result of the dialog
differently).

Ketarin-Mono-1.0.43

Fixed #15

Updated ObjectListView.cs with changes from a more recent version from
the original author.  These changes protected against the specific crash
that was reported and protected against some other potential crashes,
but still left a similar crash.  The similar crash was fixed by changing
AddRange() to Add() for individual items.  This makes the program
slower, possibly noticeably slower.

Also removed #if MONO code, since the updates from the newer
ObjectListView eliminate the need.