On 10 Feb 2009, at 20:26, Kyle Sluder wrote:
Just because it's there doesn't mean you have to use it. Granted,
we're talking about blocking I/O in the context of an application,
which needs to be pumping its runloop, but you can continue to use
read(2) and write(2) without NSPipe, as long as y
On Tue, Feb 10, 2009 at 2:24 PM, Kevin Martin wrote:
> Chances are I will write a wrapper app in the future, but I'm not familiar
> enough with
> Cocoa at the moment. Reading through the docs I can't even figure out how I
> would do non
> blocking i/o with an NSPipe, Never mind how I would communi
2) Register with the window server as an application. Use
TransformProcessType() for this.
Thanks guys. This function looks very one way though. Ideally I would
like to turn
myself into a proper application, run the dialog, and then go back to
a being a console
application. However it does
On Mon, Feb 9, 2009 at 10:54 AM, Kevin Martin wrote:
> Hi,
>
> I am pretty new to Cocoa and Objective C, so please forgive me if the answer
> is obvious. I have done a search of the archive and have found a few people
> experiencing the same problem - but no solution.
>
> I have a console applicat
On 2/9/09 3:54 PM, Kevin Martin said:
>I have a console application that I want to be able to run on both
>Windows and OS X, The only real UI related task I have is to prompt
>for paths for loading and saving files. I really prefer a nice dialog
>to asking the user to enter a path on the console.
On 9 Feb 2009, at 15:54, Kevin Martin wrote:
I have attached code that should allow you to replicate the problem.
Sorry, didn't realise I couldn't attach, Here is the code:
http://kev.khn.org.uk/nsspprob.mm.txt
Thanks,
Kevin Martin
___
Cocoa-dev
Hi,
I am pretty new to Cocoa and Objective C, so please forgive me if the
answer is obvious. I have done a search of the archive and have found
a few people experiencing the same problem - but no solution.
I have a console application that I want to be able to run on both
Windows and OS X
