On 10/02/2008, Hess, Philip J <[EMAIL PROTECTED]> wrote: > > Of course, now the app has the same issues as any Mac GUI app compiled with > GTK, in that even though it's a console app (sort of), it will only run under > X11. And > no way to compile for Carbon with lazbuild unless the framework carbon stuff > already > set in the .lpi.
That's correct. You can't include the 'interfaces' unit in a console application because it requires (pulls in) GUI code. You will not notice anything under Windows, because Windows always has a GUI installed. Under Linux it's easily noticed when you don't run a X Server and try an execute a console application that uses 'interfaces' unit. I had this same issue in the tiOPF project and console unit tests on my Linux server which doesn't run a X Window server installed. Some unit tests required the clipboard, which is a GUI feature in LCL or VCL. I had to rework the unit tests to exclude those tests when run as a true console application. > RGB value _or_ a color constant like clBtnFace (value of 15). If someone > passes a > color constant to one of these functions, they'll get an unexpected result. > So it > seems as though RedGreenBlue, etc. should either call ColorToRGB first or > else the > param type should be Again correct and what I forgot to mention in my previous post. If you pass in a clXXXX color alias (like clBtnFace etc) you first need to lookup the RGB equivalent color value via ColorToRGB. In fpGUI it's possible to do without requiring a true GUI installed, but I'm not sure what would happen under Windows etc... Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
