Re: [Lazarus] Font errors in console output on OSX

2015-06-16 Thread FreeMan
On 15.06.2015 18:04, Graeme Geldenhuys wrote: Out of interest, does LCL-Qt run on Linux, FreeBSD, Windows and OSX equally well? That might be an option too, to overcome the many LCL inconsistencies between platforms. My first working with lazarus on kubuntu. I used there qt, cross compiled to wi

Re: [Lazarus] Font errors in console output on OSX

2015-06-15 Thread zeljko
On 06/15/2015 05:04 PM, Graeme Geldenhuys wrote: On 2015-06-15 15:44, zeljko wrote: I'm using it (LCL-Qt 32bit...qt-4.7.4 carbon) for commercial (database related) appshaven't spotted problems. Good to know, thanks. For now I'll stick to LCL-Carbon, seeing that Lazarus IDE uses it too, and

Re: [Lazarus] Font errors in console output on OSX

2015-06-15 Thread Graeme Geldenhuys
On 2015-06-15 15:44, zeljko wrote: > I'm using it (LCL-Qt 32bit...qt-4.7.4 carbon) for commercial (database > related) appshaven't spotted problems. Good to know, thanks. For now I'll stick to LCL-Carbon, seeing that Lazarus IDE uses it too, and it is still the default for OSX. If I find too

Re: [Lazarus] Font errors in console output on OSX

2015-06-15 Thread zeljko
On 06/15/2015 03:56 PM, Graeme Geldenhuys wrote: On 2015-06-15 14:52, Graeme Geldenhuys wrote: Carbon is deprecated, no actual interest in fixing the issue. Is the issue with Carbon or with LCL-Carbon? Or is LCL-Qt a better option under OSX? I'm using it (LCL-Qt 32bit...qt-4.7.4 carbon) for

Re: [Lazarus] Font errors in console output on OSX

2015-06-15 Thread Dmitry Boyarintsev
On Mon, Jun 15, 2015 at 9:52 AM, Graeme Geldenhuys < mailingli...@geldenhuys.co.uk> wrote: > On 2015-06-15 14:15, Dmitry Boyarintsev wrote: > > Carbon is deprecated, no actual interest in fixing the issue. > > Is the issue with Carbon or with LCL-Carbon? > It's LCL-Carbon issue. thanks, Dmitry -

Re: [Lazarus] Font errors in console output on OSX

2015-06-15 Thread Dmitry Boyarintsev
On Mon, Jun 15, 2015 at 9:56 AM, Graeme Geldenhuys < mailingli...@geldenhuys.co.uk> wrote: > Or is LCL-Qt a better option under OSX? > > You can (should) definitely try LCL-Qt. LCL-Cocoa is the best option, but it will require lots of patience and bug reporting. thanks, Dmitry --

Re: [Lazarus] Font errors in console output on OSX

2015-06-15 Thread Graeme Geldenhuys
On 2015-06-15 14:52, Graeme Geldenhuys wrote: >> > Carbon is deprecated, no actual interest in fixing the issue. > Is the issue with Carbon or with LCL-Carbon? Or is LCL-Qt a better option under OSX? Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://

Re: [Lazarus] Font errors in console output on OSX

2015-06-15 Thread Graeme Geldenhuys
On 2015-06-15 14:15, Dmitry Boyarintsev wrote: > Carbon is deprecated, no actual interest in fixing the issue. Is the issue with Carbon or with LCL-Carbon? So am I supposed to use LCL-Cocoa instead? I thought the LCL-Cocoa widgetset is still in heavy development stage and not ready for production

Re: [Lazarus] Font errors in console output on OSX

2015-06-15 Thread Dmitry Boyarintsev
On Mon, Jun 15, 2015 at 6:55 AM, Graeme Geldenhuys < mailingli...@geldenhuys.co.uk> wrote: > > Is this normal (something that can be ignored), or is there something > wrong in the application, or in LCL-Carbon? > > Ignore it. Though you can create a bug report about it. Carbon is deprecated, no a

[Lazarus] Font errors in console output on OSX

2015-06-15 Thread Graeme Geldenhuys
Hi, When I run a fleshly compiled program of mine from the OSX Terminal, I get a lot of font error lines like the following: === graemes-mbp:puntenboek graemeg$ ./puntenboek CarbonFontIDToFontName Error: ATSUFindFontName Length failed with result -8905 CarbonFontIDToFontName E