On 5/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
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.
I am already preparing a patch. If you wait 1 or 2 days I will have it fixed.
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.
Don´t worry =) With some discussion we can choose the best solutions,
and in the process everyone learns.
Just to understand your point of view, what would be the difference between
QtPrivate and QtObjects? Why QtMemoStrings shouldn't just go into QtPrivate?
Well, simply because qtprivate is getting too big =) and this makes
maintenance hard.
There is also a clear separation between both. qtprivate should have
all classes that are visible widgets. That is, descendents of
TQtWidget.
qtobjects can have the helper classes, like Brush, String, Color,
Pallete, etc. Or better defined as any class that isn´t a visual
widget.
thanks,
--
Felipe Monteiro de Carvalho
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
