Thanks a lot, I'll proceed as suggested.
Martin
On Mar 12, 2010, at 9:07 AM, Kyle Sluder wrote:
> On Thu, Mar 11, 2010 at 11:38 PM, Martin Hewitson
> wrote:
>> Thanks, Kyle. I figured the answer would be something like this. OK, then
>> I'll need to rethink the architecture a bit. I was aiming
On Thu, Mar 11, 2010 at 11:38 PM, Martin Hewitson
wrote:
> Thanks, Kyle. I figured the answer would be something like this. OK, then
> I'll need to rethink the architecture a bit. I was aiming for an Xcode-like
> interface with potentially multiple views to the same file content, but
> without
Thanks, Kyle. I figured the answer would be something like this. OK, then I'll
need to rethink the architecture a bit. I was aiming for an Xcode-like
interface with potentially multiple views to the same file content, but without
using 'updates continuously' this is going to be more difficult to
On Thu, Mar 11, 2010 at 7:50 AM, Martin Hewitson
wrote:
> The nasty little problem I have is that if I edit the contents of a file via
> the NSTextView, then do 'undo', the cursor (selection) in the NSTextView
> jumps to the end of the document, and the scrollview jumps to the top. Almost
> as
Dear list,
I have a puzzling problem which is making my puzzler sore.
Here's the outline:
I have a core-data doc based app. I have core data entities which represent
files on disk. When the entity is created, the contents of the file are loaded
(in to a binary-data attribute called 'content').
