Carbon calls to Cocoa gadgets

[WilliamL]

With the introduction of 4.7 with gadgets that are created using Cocoa I'm wondering what happens in my old programs that modify gadgets with carbon calls? I would assume that the carbon calls wouldn't have any effect but will they also create IMA errors (getting those) or other errors? I'm guessing that carbon calls that don't involve gadgets (like printing) will still work fine in the 'x86' version.

[wilbert]

The Cocoa version of PureBasic is much different internally.
You still can use Carbon calls the OS supports but if they interact with PB objects, you will have problems.
GadgetID for example returns different kind of objects but also images are different ( Carbon uses CGImage, Cocoa uses NSImage ).
Most likely when you use Carbon API calls to modify PB gadgets and compile the same code with the Cocoa version of PB, it will crash.

[J. Baker]

Yeah, none of my ImportC functions work with the Cocoa version. I think it's best to stick with Cocoa from here on out. The way Apple is going, I wouldn't be surprised if OS X 10.9 (when that day comes) doesn't even support Carbon.

[WilliamL]

So does the carbon printing still work ok for printing strings and images/lines/boxes?

I guess I'm going to have to start looking into re-creating my printing include file ( http://www.purebasic.fr/english/viewtop ... 06#p356265 ) in Cocoa.

[wilbert]

One of the reasons for such code was the bad printing quality on OS X.
I have the impression the print quality has improved on the Cocoa version of PureBasic.

[WilliamL]

I take that as a 'yes' that carbon printing still works.. or are you saying that printing in pb with cocoa will be good enough without resorting to API?

If not, as for the cocoa printing, I'll need some help there...

[wilbert]

The code example from the PureBasic help file gives sharp text on my laser printer.
So what I was saying that it probably is good enough without any API calls.

[WilliamL]

Whew! Thanks wilbert for trying it. I'll see how it goes for me and maybe the API (for printing) will be a thing of the past.