I see that GTK/GTK2 doesn't appear to have PtInRegion implemented. That's probably why I didn't use it.
In some cases the compatibility functions still need to call the Win API regardless of widgetset if running on Windows, but you're right, if a handle is passed, that should only be passed on to Win API if LCLwin32 is defined. I'll review all the compat. functions when I have some time. Thanks. -Phil ----- "Felipe Monteiro de Carvalho" <[email protected]> wrote: > On Tue, Dec 1, 2009 at 1:24 PM, Phil Hess <[email protected]> > wrote: > > Good point, although if you recall the history of this port, it > started with the only two widgetsets that worked back then: win32 and > gtk1 - the others just came along for the ride. I'm not even sure that > LCLWin32 was defined back when I started. > > I would bet they were already defined, they are extremely old. > > > Does anyone use Qt on Windows though? That doesn't make sense to me. > Why put another layer on top of Windows when win32 works quite well? > And without any auxiliary libraries. > > Less work to port between LCL platforms. If you use LCL-Qt in all > platforms your port effort between them is minimal (if necessary), > both because you are using the same LCL-Qt codebase instead of > multiple widgetset codes with various states of supported components > and because Qt is not a native toolkit, it just looks native but has > custom painting which helps it be very consistent across platforms. > > -- > Felipe Monteiro de Carvalho > > -- > _______________________________________________ > Lazarus mailing list > [email protected] > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
