It hung because you are using synchronous calls not asynchronous,
Apple doesn't allow synchronous calls in widgets anymore
what you need to do is this:
widget.system( "/path/to/command", processOutput );
function processOutput(result) {
if(result.outputString) {
output = result.outputString;
}
}
one of the cool features of asynchronous commands is you can
dynamically assign functions like so:
var cmd = widget.system( "/path/to/command", function(output)
{ processOutput(output); } );
the latter allows you to run actions that are in a loop or require
dynamic variables that are not supported outside of the loop.
Hope that helps
On 8/25/06, Michael Kwasnicki <email@hidden> wrote:Hi,
I'm using a commandline tool to pass data to my widget this way.
var output = widget.system( "/path/to/command", null ).outputString;
I wondered why my widget hung as the passed data grew.
The data that is passed to the stdout by the command is easily
greater than 40kb.
First I thought there is a memory limit for variables in JavaScript.
But a shorter output concatenated with the same output ten times
produced far more than 40kb in that variable.
Then I noticed something odd. I was not the widget that hung. It was
the command.
Killing the command in the Activity Monitor revived the widget.
Since the command does not hung in the Terminal I think there is some
oddity in the widget.system() thing.
It even hungs on "cat longtext.txt" if longtext.txt is long enough.
That is why I'm absolutely sure that it is not the fault of my
commandline tool.
Please can someone verify that and tell me what to do?
Thanks,
Michael
