Hello, Jaroslav.

First of all, sorry for the long delay. Very busy in the last months.

2010/4/4 Jaroslav Imrich <jaroslav.imrich@gmail.com>

Hello David,

thanks for reviewing and including my previous patch. I am attaching
new one that fixes following problems:

Problem no.1 -  G_GUINT64_FORMAT
This is the platform dependent conversion specifier for scanning and
printing values of type guint64. It is replaced by "llu" on Linux and
by "I64" on Windows and it works great with GTK stuff but sqlite does
not support "I64" modifier and caused gnomint to segfault. So first I
globally redefined this macro to "llu" but then GTK started to cause
segfaults. Then I was also thinking about adding support for this type
to sqlite but when I saw their code I decided not to do that :) So I
just introduced new define in gnoMint code called
GNOMINT_GUINT64_FORMAT and modified all SQL strings to utilise it.

Perfect. Applied.
Problem no.2 - G_MODULE_EXPORT
I've found two more callbacks in trunk that needed G_MODULE_EXPORT, so
I added it.

Problem no.3 - Displaying certificate properties caused SEGFAULT
I've found that g_strdup_printf() was not used properly in
which caused segfault, so I modified it according to documentation
available at http://library.gnome.org/devel/glib/unstable/glib-String-Utility-Functions.html#g-strdup-printf

Thanks a lot!
After these fixes gnoMint on windows seems to be more stable now, but
there is a lot of testing that needs to be done and I have few

Question no.1:
What command do you use in svn trunk to generate configure script? I
tried running "autoconf" without any parameters on windows and also on
linux, but it displayed few errors and generated "configure" script
that was unusable.

I usually execute ./autogen.sh
Question no.2:
There is a file called "doc/test_plan.txt" in trunk and last revision
of this file is from 19.11.2007. It would be great if you could update
this plan (if needed) so it can be used to confirm that windows port
is working corretly. I think that properly written, this document
could not only be the test plan but also a user guide covering all the
feautures of gnoMint. I know it may seem to be a lot of work, but I am
sure that it can be done faster and easier if we could leverage some
sort of collaboration platform (wiki or google docs perhaps).

Uff. That's a good idea, but I don't have enough time.

If you want, I can give you permissions in the project, so you can colaborate directly over the official repository.
Oh, and could you please change my e-mail in AUTHORS file to
jariq(at)jariq(dot)sk ? Thanks a lot.

Done in git repository.

Kind regards.

David Marín Carreño