Fwd: [Kde-java] A curious problem with QSqlCursor

[David Goodenough]

Looking at this further, when you create a java QSqlCursor this results in a
C++ QSqlCursorBridge which is derived from the C++ QSqlCursor being
created.  The calculateField method is not declared as part of that
sub-classing, so it never gets called.  The QSqlCursorBridge class should
include this method, and then that method should call the calculateField
method in the java class, taking care as with the polish method not to
have a recursion problem.  The default method for this class should
call the C++ default method.

Now I presume that these callbacks, like polish, are declared by the
code that generates these bridge classes based on something like
their being virtual?  If so I am confused why the virtual methods of
QSqlCursor are not being processed, as calculateField is virtual (at
least in the the version of qsqlcursor.h that is installed on my machine.
The only difference I can see is that polish is a public method, while
calculateField is a protected method.  However I get lost reading 
Perl scripts, and as kalyptus is a Perl script I got well and truely
lost.

David
-------------- next part --------------
An embedded message was scrubbed...
From: David Goodenough <david.goodenough at btconnect.com>
Subject: [Kde-java] A curious problem with QSqlCursor
Date: Mon, 25 Oct 2004 09:26:10 +0100
Size: 5061
Url: http://mail.kde.org/pipermail/kde-java/attachments/20041025/b55bba77/attachment.mht