I'm using a simple application that can be run from the command line (on OSX) like so:
oconv inFile.rad > outFile.rad
When run from the command line, the output file looks like this:
#?RADIANCE
oconv inFile.rad
FORMAT=Radiance_octree
0.57499 0.28749 0.28749 1.55002 inFile.rad
I want to package this app with my AIR 2.0 application and run via Native Process. But when I try to run this file via AIR's nativeProcess, the output of the process gets truncated somehow. All that comes in to StandardOutput is
#?RADIANCE
/Users/daniel/LBNL/COMFEN3_1/radiance/oconv scenario.rad
FORMAT=Radiance_octree
0.57499
Does anybody know why AIR would truncate the data coming into StandardOutput? I wish I could use the I/O redirect character > in my arguments, but that doesn't seem to work either. I can't do this:
var startupInfo:NativeProcessStartupInfo = new NativeProcessStartupInfo()
var args:Vector.<String> = new Vector.<String>();
args.push("inFile.rad")
args.push(">")
args.push("outFile.rad")
startupInfo.arguments = args
or this
var startupInfo:NativeProcessStartupInfo = new NativeProcessStartupInfo()
var args:Vector.<String> = new Vector.<String>();
args.push("inFile.rad")
args.push(">")
args.push("outFile.rad")
startupInfo.arguments = args
Has anybody experienced the truncation problem? Or, has anybody even gotten a I/O redirection to work via the arguments Vector?
Thanks for any thoughts,
Daniel