Mac OS X Fonts Messages in syslog

[Gerhard Mueller]

Using wxWidgets 3.1, Xcode 5.0.2 and Mavericks I get lots of this messages
in syslog:

13.01.14 22:06:00,966 OpenCPN[1154]: CoreText performance note: Client

called CTFontCreateWithName() using name ".Lucida Grande UI" and got font
with PostScript name ".LucidaGrandeUI". For best performance, only use
PostScript names when calling this API.
13.01.14 22:48:35,363 OpenCPN[1420]: CoreText performance note: Set a
breakpoint on CTFontLogSuboptimalRequest to debug.

Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is used in
my application OpenCPN. Also I cannot find these functions in the wxWidgets
sources.

However I get these messages also with another application which uses
obviously wxWidgets:

13.01.14 18:20:32,007 Poedit[469]: CoreText performance note: Client called

CTFontCreateWithName() using name ".Lucida Grande UI" and got font with
PostScript name ".LucidaGrandeUI". For best performance, only use
PostScript names when calling this API.
13.01.14 18:45:48,503 Poedit[537]: CoreText performance note: Set a
breakpoint on CTFontLogSuboptimalRequest to debug.

What is going on here?

Gerhard

[Vadim Zeitlin]

On Tue, 14 Jan 2014 05:27:15 -0800 (PST) Gerhard Mueller wrote:

GM> 13.01.14 22:06:00,966 OpenCPN[1154]: CoreText performance note: Client
GM> > called CTFontCreateWithName() using name ".Lucida Grande UI" and got font
GM> > with PostScript name ".LucidaGrandeUI". For best performance, only use
GM> > PostScript names when calling this API.
GM> >
GM> > 13.01.14 22:48:35,363 OpenCPN[1420]: CoreText performance note: Set a
GM> > breakpoint on CTFontLogSuboptimalRequest to debug.

Have you tried doing what it advises, i.e. set this breakpoint?

GM> Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is used in
GM> my application OpenCPN. Also I cannot find these functions in the wxWidgets
GM> sources.

CTFontCreateWithName() is definitely used by wxOSX.

GM> What is going on here?

It looks like the names of the fonts to use have changed but I really
don't know anything about it.

Regards,
VZ

[Gerhard Mueller]

Vadim,

Post by Vadim Zeitlin
GM> 13.01.14 22:06:00,966 OpenCPN[1154]: CoreText performance note: Client
GM> > called CTFontCreateWithName() using name ".Lucida Grande UI" and got font
GM> > with PostScript name ".LucidaGrandeUI". For best performance, only use
GM> > PostScript names when calling this API.
GM> >
GM> > 13.01.14 22:48:35,363 OpenCPN[1420]: CoreText performance note: Set a
GM> > breakpoint on CTFontLogSuboptimalRequest to debug.
Have you tried doing what it advises, i.e. set this breakpoint?

I cannot set a breakpoint because I cannot find the function
CTFontLogSuboptimalReques() neither in my app code nor in the wxWidgets
sources.

Post by Vadim Zeitlin
GM> Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is used in
GM> my application OpenCPN. Also I cannot find these functions in the wxWidgets
GM> sources.
CTFontCreateWithName() is definitely used by wxOSX.

Yes, I have found CTFontCreateWithName() used in wxWidgets
src/osx/carbon/font.cpp
It has a TODO remark there. So it seems something is missing in the
wxWidgets code.

Post by Vadim Zeitlin
GM> What is going on here?
It looks like the names of the fonts to use have changed but I really
don't know anything about it.

So I suggest to put this issue into the wxWidgets bug list.
After all it seems all applications using wxWidgets are affected on Mac OS
X.

Regards,

Post by Vadim Zeitlin
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/

[Vadim Zeitlin]

On Tue, 14 Jan 2014 08:30:17 -0800 (PST) Gerhard Mueller wrote:

GM> > Have you tried doing what it advises, i.e. set this breakpoint?
GM> >
GM> I cannot set a breakpoint because I cannot find the function
GM> CTFontLogSuboptimalReques() neither in my app code nor in the wxWidgets
GM> sources.

You don't need to find it. Just do "b CTFontLogSuboptimalRequest" on gdb
prompt.

Regards,
VZ

[Gerhard Mueller]

I am not on Linux, I use Xcode on Mac OS X.

I should ask Stefan Csomor. Maybe he knows something.

Gerhard

Post by Vadim Zeitlin
GM> > Have you tried doing what it advises, i.e. set this breakpoint?
GM> >
GM> I cannot set a breakpoint because I cannot find the function
GM> CTFontLogSuboptimalReques() neither in my app code nor in the wxWidgets
GM> sources.
You don't need to find it. Just do "b CTFontLogSuboptimalRequest" on gdb
prompt.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/

[Vadim Zeitlin]

On Tue, 14 Jan 2014 09:11:42 -0800 (PST) Gerhard Mueller wrote:

GM> I am not on Linux, I use Xcode on Mac OS X.

gdb also runs under OS X and all you need to do is to run your program
under it, set this breakpoint and do "bt" when it's hit. And, FWIW, Xcode
gives, or at least used to give, you access to gdb too (as well as a way to
set a breakpoint on function name, somewhere inside its myriad of menus,
I'm sure).

Regards,
VZ

[Gerhard Mueller]

Vadim,

Post by Vadim Zeitlin
GM> 13.01.14 22:06:00,966 OpenCPN[1154]: CoreText performance note: Client
GM> > called CTFontCreateWithName() using name ".Lucida Grande UI" and got font
GM> > with PostScript name ".LucidaGrandeUI". For best performance, only use
GM> > PostScript names when calling this API.
GM> >
GM> > 13.01.14 22:48:35,363 OpenCPN[1420]: CoreText performance note: Set a
GM> > breakpoint on CTFontLogSuboptimalRequest to debug.
Have you tried doing what it advises, i.e. set this breakpoint?

I cannot set a breakpoint because I cannot find the function
CTFontLogSuboptimalReques() neither in my app code nor in the wxWidgets
sources.

Post by Vadim Zeitlin
GM> Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is used in
GM> my application OpenCPN. Also I cannot find these functions in the wxWidgets
GM> sources.
CTFontCreateWithName() is definitely used by wxOSX.

Yes, I have found CTFontCreateWithName() used in wxWidgets
src/osx/carbon/font.cpp
It has a TODO remark there. So it seems something is missing in the
wxWidgets code.

Post by Vadim Zeitlin
GM> What is going on here?
It looks like the names of the fonts to use have changed but I really
don't know anything about it.

So I suggest to put this issue into the wxWidgets bug list.
After all it seems all applications using wxWidgets are affected on Mac OS
X.

Regards,

Post by Vadim Zeitlin
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/

[Stefan Csomor]

Hi

Using wxWidgets 3.1, Xcode 5.0.2 and Mavericks I get lots of this messages in syslog:

13.01.14 22:06:00,966 OpenCPN[1154]: CoreText performance note: Client called CTFontCreateWithName() using name ".Lucida Grande UI" and got font with PostScript name ".LucidaGrandeUI". For best performance, only use PostScript names when calling this API.

13.01.14 22:48:35,363 OpenCPN[1420]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.

Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is used in my application OpenCPN. Also I cannot find these functions in the wxWidgets sources.

you shouldn't get a lot of these warnings, are you always recreating wxFonts ? if possible you should keep them around

Best,

Stefan

[Gerhard Mueller]

So there is no way to call CTFontCreateWithName() with the correct font
names? Is this a bug in OS X or in wxWidgets?

Gerhard

Post by Gerhard Mueller
Hi
13.01.14 22:06:00,966 OpenCPN[1154]: CoreText performance note: Client

called CTFontCreateWithName() using name ".Lucida Grande UI" and got font
with PostScript name ".LucidaGrandeUI". For best performance, only use
PostScript names when calling this API.
13.01.14 22:48:35,363 OpenCPN[1420]: CoreText performance note: Set a
breakpoint on CTFontLogSuboptimalRequest to debug.

Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is used in
my application OpenCPN. Also I cannot find these functions in the wxWidgets
sources.
you shouldn't get a lot of these warnings, are you always recreating
wxFonts ? if possible you should keep them around
Best,
Stefan

[Robin Dunn]

Post by Gerhard Mueller
Hi
Using wxWidgets 3.1, Xcode 5.0.2 and Mavericks I get lots of this
Client called CTFontCreateWithName() using name ".Lucida Grande
UI" and got font with PostScript name ".LucidaGrandeUI". For
best performance, only use PostScript names when calling this API.
Set a breakpoint on CTFontLogSuboptimalRequest to debug.
Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is
used in my application OpenCPN. Also I cannot find these functions
in the wxWidgets sources.
you shouldn't get a lot of these warnings, are you always recreating
wxFonts ? if possible you should keep them around

FWIW, Qt has had what looks like the same issue.

https://bugreports.qt-project.org/browse/QTBUG-32789
--
Robin Dunn
Software Craftsman
http://wxPython.org

[Stefan Csomor]

Hi

Post by Robin Dunn

Post by Gerhard Mueller
Hi
Using wxWidgets 3.1, Xcode 5.0.2 and Mavericks I get lots of this
Client called CTFontCreateWithName() using name ".Lucida Grande
UI" and got font with PostScript name ".LucidaGrandeUI". For
best performance, only use PostScript names when calling this API.
Set a breakpoint on CTFontLogSuboptimalRequest to debug.
Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is
used in my application OpenCPN. Also I cannot find these functions
in the wxWidgets sources.
you shouldn't get a lot of these warnings, are you always recreating
wxFonts ? if possible you should keep them around

FWIW, Qt has had what looks like the same issue.
https://bugreports.qt-project.org/browse/QTBUG-32789

no that's not the same issue, did you post the wrong link ? our issue is a
performance warning we are getting because we are using the Family Name
instead of the PostScript Name.

Best,

Stefan

[Gerhard Mueller]

Stefan,

it seems the bug has been solved in Qt but not in wxWidgets right now:

See: https://bugreports.qt-project.org/browse/QTBUG-32789
and read, it is (was) the same issue as in wxWidgets.

Should I switch my program to Qt from wxWidgets although that is a lot of
work for me?

Gerhard

Post by Stefan Csomor
Hi

Post by Robin Dunn

Post by Gerhard Mueller
Hi
Using wxWidgets 3.1, Xcode 5.0.2 and Mavericks I get lots of this
Client called CTFontCreateWithName() using name ".Lucida Grande
UI" and got font with PostScript name ".LucidaGrandeUI". For
best performance, only use PostScript names when calling this API.
Set a breakpoint on CTFontLogSuboptimalRequest to debug.
Neither CTFontCreateWithName() nor CTFontLogSuboptimalRequest() is
used in my application OpenCPN. Also I cannot find these functions
in the wxWidgets sources.
you shouldn't get a lot of these warnings, are you always recreating
wxFonts ? if possible you should keep them around

FWIW, Qt has had what looks like the same issue.
https://bugreports.qt-project.org/browse/QTBUG-32789

no that's not the same issue, did you post the wrong link ? our issue is a
performance warning we are getting because we are using the Family Name
instead of the PostScript Name.
Best,
Stefan

[Stefan Csomor]

Hi

Von: Gerhard Mueller <***@googlemail.com<mailto:***@googlemail.com>>
Antworten an: "wx-***@googlegroups.com<mailto:wx-***@googlegroups.com>" <wx-***@googlegroups.com<mailto:wx-***@googlegroups.com>>
Datum: Dienstag, 22. April 2014 12:12
An: "wx-***@googlegroups.com<mailto:wx-***@googlegroups.com>" <wx-***@googlegroups.com<mailto:wx-***@googlegroups.com>>
Betreff: Re: Mac OS X Fonts Messages in syslog

Stefan,

it seems the bug has been solved in Qt but not in wxWidgets right now:

See: https://bugreports.qt-project.org/browse/QTBUG-32789
and read, it is (was) the same issue as in wxWidgets.

Should I switch my program to Qt from wxWidgets although that is a lot of work for me?

The problem is not the same, wx does not hardcode the font's name. but refers to the system font by constants as it is recommended. The performance warning occurs because of the externally presented human readable font names and their internal name. trunk has been updated to cache the name conversion between human readable names and postscript names. So the warning occurs once per font which still is faster than precaching all fontnames.

Best,

Stefan

[Gerhard Mueller]

I don't know anything about internals of wxWidgets or Qt.
Is there any function in wxWidgets to get rid of the ugly messages like in
Qt?
In Qt they obviously use: QFont::insertSubstitution(".Lucida Grande UI",
"Lucida Grande");

Gerhard

Post by Stefan Csomor
Hi
Datum: Dienstag, 22. April 2014 12:12
Betreff: Re: Mac OS X Fonts Messages in syslog
Stefan,
See: https://bugreports.qt-project.org/browse/QTBUG-32789
and read, it is (was) the same issue as in wxWidgets.
Should I switch my program to Qt from wxWidgets although that is a lot of work for me?
The problem is not the same, wx does not hardcode the font's name. but
refers to the system font by constants as it is recommended. The
performance warning occurs because of the externally presented human
readable font names and their internal name. trunk has been updated to
cache the name conversion between human readable names and postscript
names. So the warning occurs once per font which still is faster than
precaching all fontnames.
Best,
Stefan

[w***@gmail.com]

Post by Stefan Csomor

Post by Robin Dunn
FWIW, Qt has had what looks like the same issue.
https://bugreports.qt-project.org/browse/QTBUG-32789

no that's not the same issue, did you post the wrong link ? our issue is a
performance warning we are getting because we are using the Family Name
instead of the PostScript Name.

From what I understand they had this:
https://codereview.qt-project.org/69321

Pass postscript font name to CTFontCreateWithName

This removes the the "CoreText performance note"
console warnings.

but then it was superseded by the ticket Robin linked to and fixed here:

https://qt.gitorious.org/qt/qt/commit/98352b964f8a11751af89813c9524c35b67a5633

Marcin

[Gerhard Mueller]

Marcin,

yes, I see, they have fixed that in Qt anyhow.
But why they could not fix that in wxWidgets?
It's another argument for me not to use wxWidgets anymore.

Gerhard

Post by w***@gmail.com

Post by Stefan Csomor

Post by Robin Dunn
FWIW, Qt has had what looks like the same issue.
https://bugreports.qt-project.org/browse/QTBUG-32789

no that's not the same issue, did you post the wrong link ? our issue is a
performance warning we are getting because we are using the Family Name
instead of the PostScript Name.

https://codereview.qt-project.org/69321
Pass postscript font name to CTFontCreateWithName
This removes the the "CoreText performance note"
console warnings.
https://qt.gitorious.org/qt/qt/commit/98352b964f8a11751af89813c9524c35b67a5633
Marcin

[Marcin Wojdyr]

Gerhard,
the best way to push such fix is to prepare a patch and test it on as
many OSX versions as you can
Marcin

Post by Gerhard Mueller
Marcin,
yes, I see, they have fixed that in Qt anyhow.
But why they could not fix that in wxWidgets?
It's another argument for me not to use wxWidgets anymore.
Gerhard

Post by w***@gmail.com

Post by Stefan Csomor

Post by Robin Dunn
FWIW, Qt has had what looks like the same issue.
https://bugreports.qt-project.org/browse/QTBUG-32789

no that's not the same issue, did you post the wrong link ? our issue is a
performance warning we are getting because we are using the Family Name
instead of the PostScript Name.

https://codereview.qt-project.org/69321
Pass postscript font name to CTFontCreateWithName
This removes the the "CoreText performance note"
console warnings.
https://qt.gitorious.org/qt/qt/commit/98352b964f8a11751af89813c9524c35b67a5633
Marcin

--
Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
or visit http://groups.google.com/group/wx-users

[Stefan Csomor]

Hi

I had written the code using a font descriptor lookup many years ago, it
is still in the sources, I had to deactivate it because it was a lot
slower than the built-in CreateWithName fallbacks, but I'll mix it in
again, and use it once per fontname, that way the performance warning goes
away, and I afterwards add the family and postscript names to the cache so
that the next time the same font is asked for I can use CreateWithNAme
directly. So the speed problem doesn't occur.

Best,

Stefan

-----Ursprüngliche Nachricht-----
Von: Marcin Wojdyr <***@gmail.com>
Antworten an: "wx-***@googlegroups.com" <wx-***@googlegroups.com>
Datum: Mittwoch, 23. April 2014 13:45
An: "wx-***@googlegroups.com" <wx-***@googlegroups.com>
Betreff: Re: Mac OS X Fonts Messages in syslog

Post by Marcin Wojdyr
Gerhard,
the best way to push such fix is to prepare a patch and test it on as
many OSX versions as you can
Marcin

Post by Gerhard Mueller
Marcin,
yes, I see, they have fixed that in Qt anyhow.
But why they could not fix that in wxWidgets?
It's another argument for me not to use wxWidgets anymore.
Gerhard

Post by w***@gmail.com

Post by Stefan Csomor

Post by Robin Dunn
FWIW, Qt has had what looks like the same issue.
https://bugreports.qt-project.org/browse/QTBUG-32789

no that's not the same issue, did you post the wrong link ? our issue
is
a
performance warning we are getting because we are using the Family Name
instead of the PostScript Name.

https://codereview.qt-project.org/69321
Pass postscript font name to CTFontCreateWithName
This removes the the "CoreText performance note"
console warnings.
https://qt.gitorious.org/qt/qt/commit/98352b964f8a11751af89813c9524c35b6
7a5633
Marcin

--
Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
or visit http://groups.google.com/group/wx-users

--
Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
or visit http://groups.google.com/group/wx-users

[Stefan Csomor]

committed in r76393 <http://trac.wxwidgets.org/changeset/76393>

Best,

Stefan

-----Ursprüngliche Nachricht-----
Von: Stefan Csomor <***@advancedconcepts.ch>
Antworten an: "wx-***@googlegroups.com" <wx-***@googlegroups.com>
Datum: Mittwoch, 23. April 2014 14:16
An: "wx-***@googlegroups.com" <wx-***@googlegroups.com>
Betreff: Re: Mac OS X Fonts Messages in syslog

Post by Stefan Csomor
Hi
I had written the code using a font descriptor lookup many years ago, it
is still in the sources, I had to deactivate it because it was a lot
slower than the built-in CreateWithName fallbacks, but I'll mix it in
again, and use it once per fontname, that way the performance warning goes
away, and I afterwards add the family and postscript names to the cache so
that the next time the same font is asked for I can use CreateWithNAme
directly. So the speed problem doesn't occur.
Best,
Stefan
-----Ursprüngliche Nachricht-----
Datum: Mittwoch, 23. April 2014 13:45
Betreff: Re: Mac OS X Fonts Messages in syslog

Post by Marcin Wojdyr
Gerhard,
the best way to push such fix is to prepare a patch and test it on as
many OSX versions as you can
Marcin

Post by Gerhard Mueller
Marcin,
yes, I see, they have fixed that in Qt anyhow.
But why they could not fix that in wxWidgets?
It's another argument for me not to use wxWidgets anymore.
Gerhard

Post by w***@gmail.com

Post by Stefan Csomor

Post by Robin Dunn
FWIW, Qt has had what looks like the same issue.
https://bugreports.qt-project.org/browse/QTBUG-32789

no that's not the same issue, did you post the wrong link ? our issue
is
a
performance warning we are getting because we are using the Family Name
instead of the PostScript Name.

https://codereview.qt-project.org/69321
Pass postscript font name to CTFontCreateWithName
This removes the the "CoreText performance note"
console warnings.
https://qt.gitorious.org/qt/qt/commit/98352b964f8a11751af89813c9524c35b
6
7a5633
Marcin

--
Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
or visit http://groups.google.com/group/wx-users

--
Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
or visit http://groups.google.com/group/wx-users

--
Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
or visit http://groups.google.com/group/wx-users

[Vadim Zeitlin]

On Wed, 23 Apr 2014 04:26:59 -0700 (PDT) Gerhard Mueller wrote:

GM> yes, I see, they have fixed that in Qt anyhow.
GM> But why they could not fix that in wxWidgets?
GM> It's another argument for me not to use wxWidgets anymore.

You repeatedly seem to be looking for an excuse to not use wxWidgets. I
don't really understand this, who is forcing you to use it? If you don't
want to use it, this is absolutely not a problem at all but it seems rather
strange to repeatedly post it to the wxWidgets list. What are you trying to
achieve exactly?

As for the bug itself, I'm not a Mac expert, but AFAICS there is simply no
real problem at all since Stefan's fixes. But, again, I don't have the
impression that you are interested in solving anything anyhow.

Are you?
VZ

[Gerhard Mueller]

Sorry not to have told the background.
I am trying to make run a project for Mac OS X which was done by several
programmers for Windows and Linux during the last 5 years with wxWidgets.

Gerhard

Post by Vadim Zeitlin
GM> yes, I see, they have fixed that in Qt anyhow.
GM> But why they could not fix that in wxWidgets?
GM> It's another argument for me not to use wxWidgets anymore.
You repeatedly seem to be looking for an excuse to not use wxWidgets. I
don't really understand this, who is forcing you to use it? If you don't
want to use it, this is absolutely not a problem at all but it seems rather
strange to repeatedly post it to the wxWidgets list. What are you trying to
achieve exactly?
As for the bug itself, I'm not a Mac expert, but AFAICS there is simply no
real problem at all since Stefan's fixes. But, again, I don't have the
impression that you are interested in solving anything anyhow.
Are you?
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/

[Gerhard Mueller]

Since last changes to wxWidgets these messages have completely gone now in
my project.
So the issue was solved forever I guess.

Gerhard

Post by Gerhard Mueller
Sorry not to have told the background.
I am trying to make run a project for Mac OS X which was done by several
programmers for Windows and Linux during the last 5 years with wxWidgets.
Gerhard

Post by Vadim Zeitlin
GM> yes, I see, they have fixed that in Qt anyhow.
GM> But why they could not fix that in wxWidgets?
GM> It's another argument for me not to use wxWidgets anymore.
You repeatedly seem to be looking for an excuse to not use wxWidgets. I
don't really understand this, who is forcing you to use it? If you don't
want to use it, this is absolutely not a problem at all but it seems rather
strange to repeatedly post it to the wxWidgets list. What are you trying to
achieve exactly?
As for the bug itself, I'm not a Mac expert, but AFAICS there is simply no
real problem at all since Stefan's fixes. But, again, I don't have the
impression that you are interested in solving anything anyhow.
Are you?
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/

[Sean Duffy]

Hi, I'm also having this problem and I'm unsure how to go about fixing it.
I'm also running OS X Mavericks, writing a program with wxPython. Thanks in
advance.

Sean

Post by Gerhard Mueller
Since last changes to wxWidgets these messages have completely gone now in
my project.
So the issue was solved forever I guess.
Gerhard

Post by Gerhard Mueller
Sorry not to have told the background.
I am trying to make run a project for Mac OS X which was done by several
programmers for Windows and Linux during the last 5 years with wxWidgets.
Gerhard

Post by Vadim Zeitlin
GM> yes, I see, they have fixed that in Qt anyhow.
GM> But why they could not fix that in wxWidgets?
GM> It's another argument for me not to use wxWidgets anymore.
You repeatedly seem to be looking for an excuse to not use wxWidgets. I
don't really understand this, who is forcing you to use it? If you don't
want to use it, this is absolutely not a problem at all but it seems rather
strange to repeatedly post it to the wxWidgets list. What are you trying to
achieve exactly?
As for the bug itself, I'm not a Mac expert, but AFAICS there is simply no
real problem at all since Stefan's fixes. But, again, I don't have the
impression that you are interested in solving anything anyhow.
Are you?
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/