>-- Original Message --
>Date: Mon, 8 May 2006 20:02:52 -0300
>From: "Felipe Monteiro de Carvalho" <[EMAIL PROTECTED]>
>To: [email protected]
>Subject: Re: [lazarus] Qt patch for TMemo and Tedit.
>Reply-To: [email protected]
>
>
>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.
>
Understood.
>> 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. It had escaped me. I had put it there just at the beginning,
and then I forgot. I'll try and fix it.
>> 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.
>
I'm not in love with qtmemostrings.inc. To be frank I found it quite horrible,
(the IFDEF MEMOHEADER trick is atrocious) but as I'm cautiously moving my
first steps on an unknown ground, I started trying to change as little as
possible.
Just to understand your point of view, what would be the difference between
QtPrivate and QtObjects? Why QtMemoStrings shouldn't just go into QtPrivate?
Giuliano
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
