4606 Views 4 Replies Latest reply: May 8, 2010 3:03 PM by Grant Bennet-Alder
I did quite a bit of compatibility testing as the various versions of CarbonLib came out. I found some bugs but in general, the higher the version, the more stable the result.
Also, CarbonLib is VERY passive. That is, it only becomes active when an application requests it. And applications only request it if they have been modified to run with OS X.
Lots of stuff wasn't modified.
I suggest that you use the Extension Manager and deactivate it as a test. You may find that it isn't used at all - thus making the source of your problem something entirely different.