Have you tried running the command outside of the Dashboard
environment? Is the performance poor there too? Perhaps the command
itself is the problem. Alternatively, you could call the command
asynchronously from the widget, so that the command won't block
further execution of the widget. You need to register a handler to
be called on completion.
On Aug 25, 2006, at 9:56 AM, Michael Kwasnicki 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?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Dashboard-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/dashboard-dev/email@hidden
This email sent to email@hidden
