Fixed it (kind of).
Moving the executable into a carbon bundle seemed to sort the messaging issue out.
Unfortunately the whole point of the exercise was to add an output window to a command line application, but it is better than nothing I suppose.
Rant:
It took me a total of 25...
squart> I will give that a try, thanks.
kainjow> I would prefer to use cocoa if I was writing a new application. The software I am trying to port is a command line app at heart - the window is pretty much optional & mainly for output. Carbon seemed a better fit for the existing architecture.
It is easy enough to build a multi dimensional FFT routine if you have a 1D version.
http://en.wikipedia.org/wiki/Fast_Fourier_transform#Multidimensional_FFT_algorithms
Hi,
I am porting a simple app to MacOS at the moment. It is a command line program which needs a single window for output.
At the moment I have a test harness which does the following:
I have created a window with CreateNewWindow (document class, standard attributes).
Then I make it...