Nicola Pero wrote:
Richard latest changes to NSData caused that the NSSavePanel now
complains, if it cannot find a .hidden file in a directory:
2002-10-05 13:21:29.687 Ink[1323] File NSData.m: 219. In
readContentsOfFile Open (/.hidden) attempt failed - No such file or
> >>Richard latest changes to NSData caused that the NSSavePanel now
> >>complains, if it cannot find a .hidden file in a directory:
> >>
> >>2002-10-05 13:21:29.687 Ink[1323] File NSData.m: 219. In
> >>readContentsOfFile Open (/.hidden) attempt failed - No such file or
> >>directory
> >
> >
Nicola Pero wrote:
>>Richard latest changes to NSData caused that the NSSavePanel now
>>complains, if it cannot find a .hidden file in a directory:
>>
>>2002-10-05 13:21:29.687 Ink[1323] File NSData.m: 219. In
>>readContentsOfFile Open (/.hidden) attempt failed - No such file or
>>directory
>
> Richard latest changes to NSData caused that the NSSavePanel now
> complains, if it cannot find a .hidden file in a directory:
>
> 2002-10-05 13:21:29.687 Ink[1323] File NSData.m: 219. In
> readContentsOfFile Open (/.hidden) attempt failed - No such file or
> directory
I'm not sure if it i
> Hi Nicola,
>
> could you please give a bit more details for the following sentence:
>
> Nicola Pero wrote:
> > I'd say that standard non-rich editing is very usable.
>
> Why do you restrict this statement to "non-rich editing".
I said that 'non-rich editing is very usable' ... I ignored th
Richard latest changes to NSData caused that the NSSavePanel now
complains, if it cannot find a .hidden file in a directory:
2002-10-05 13:21:29.687 Ink[1323] File NSData.m: 219. In
readContentsOfFile Open (/.hidden) attempt failed - No such file or
directory
The questions is of course, if we
Hi Nicola,
could you please give a bit more details for the following sentence:
Nicola Pero wrote:
> I'd say that standard non-rich editing is very usable.
Why do you restrict this statement to "non-rich editing". As far as I
know, editing for RFT and non-rich text is implemented with
exactly
