Applescript question

[James Moore]

It does appear to be a bug in Outliner. I'll file a bug report based on 
these emails. Hopefully we'll be able to iron out these kinds of issues 
during the beta period.

-James

Technical Support Engineer
Omni Group


On Jan 18, 2004, at 1:27 AM, BJ Terry wrote:

> That appears to be a bug in Omni-Outliner. If you change the line 
> which reads:
>
> make new column at end
>
> to
>
> make new column at end with properties {title:"Parent", type:plain 
> text, summary type:none}
>
> it allows you to save it. I don't know why this is necessary. I knew 
> that it had to be one of the uninitialized properties that was causing 
> the error, so I added these explicit calls throughout the code, one at 
> a time, until one just made it work. I tested it with just that change 
> though, and it works on my machine, so it should be fine now. I never 
> thought to save my test documents.
>
> BJ
>
> On Jan 17, 2004, at 11:50 PM, Richard Sandilands wrote:
>
>> BJ's script works perfectly in that the resulting document is exactly
>> what I was after.
>>
>> However, the new document can't be saved nor can items be copied or
>> dragged to a new document.
>>
>> In the latter case, OO throws the following error:
>>
>> *** -[NSCFDictionary setObject:forKey:]: attempt to insert nil value
>>
>>
>> Thought I'd let you know.
>>
>> Richard Sandilands
>
> _______________________________________________
> OmniOutliner-Users mailing list
> OmniOutliner-Users at omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/omnioutliner-users