On 15/10/06, Marc Weustink <[EMAIL PROTECTED]> wrote:
Thats why I prefer a handle per widget. I don't like widgetset which
paint all them selves.
I don't see an issue with painting widgets ourselves. As far as I
know, Qt does the same. They don't inherit the native widgets,
everything was designed from the ground up. This is what fpGUI does,
and so far the Windows widgets look identical to Win2000. WinXP will
follow a little later - there are more pressing priorities.
Even with customdrawn subcontrols, I see a benefit in clipping you will
get when you use a handle per widget.
Yeah, that would be a nice bonus!
> So based on those numbers it is pretty safe to allocate handles per
> widget in a Windows platform. I can think you would reach that limit
> easily.
YM, you wouldn't ?
Yes sorry, I meant I can't think you would reach that limit easily. I
did a " xwininfo -tree" on a form created with Lazarus and the Gtk1
widget set. Gtk1 also uses window handles (id's) per widget.
Don't know if you can partially paint windows on X11, but I would avoid
updating a whole form each time some control has changed.
Yes, I do partial painting on X11. I guess this answers my question
then. If it works for Gtk, it can work for fpGUI, having multiple
window handles (one per widget), plus you get the extra benefit of
clipping, etc. Time to change fpGUI then.
Thanks for everybody that replied.
Regards,
- Graeme -
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
