On 5/8/06, Giuliano Colla <[EMAIL PROTECTED]> wrote:
I did simply follow what had been made in other interfaces:
Caraful that if you looked at Gtk interface code there are various
deprecated things there that should acctually be implemented on
another way on new interfaces. When I started the Qt interface the
first thing I did was to implement CreateComponent ..... until someone
told me that is deprecated and I should acctually implement
CreateHandle. But if you look at Gtk it uses CreateComponent a lot.
I don't see a SetText calling QTextEdit_append only.
It´s on qtwscontrols.pp, here:
class procedure TQtWSWinControl.SetText(const AWinControl:
TWinControl; const AText: string);
var
AString: WideString;
begin
if AWinControl = nil then exit;
if not AWinControl.HandleAllocated then exit;
AString := AText;
case AWinControl.fCompStyle of
csEdit,csSpinedit:
QLineEdit_setText(QLineEditH(TQtWidget(AWinControl.Handle).Widget),@AString);
//csStaticText:
csMemo:
QTextEdit_append(QTextEditH(TQtWidget(AWinControl.Handle).Widget),@AString);
end;
end;
For csMemo it only calls append and Memo doesn´t have it´s own SetText
property so the one from WinControl will be utilized.
You're right, but, on the other hand keeping the same file structure for
different interfaces makes it much easier for subsequent developers to
navigate across sources. This file scheme is the same as in gtk/gtk2 and
win32. Let's think over it a bit.
Some things implemented on qt interface are independent of LCL. This
things are necessary complements to Qt Bindings. QtPrivate generates a
object-oriented interface to the bindings. This unit could be utilized
by any Free Pascal - Qt software and qtobjects would be another part
of the object-oriented bindings.
thanks,
--
Felipe Monteiro de Carvalho
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
