Controlling iOS scrolling

is always centred in the scrollview? Ideally with swish decelerating taking place, looking like the user lined it up perfectly each time the scrolling comes to rest. Thanks in advance for any pointers, Ken - - - - - - - - - - Dr. Ken Tabb Mac, iOS & UNIX Developer - Health & Human Sciences

Re: Using Core Data ManagedObjectIDs to uniquely name files

sh of the file, which would also let you know if the file had changed, if that was of interest to you. HTH Gideon On 06/04/2010, at 9:27 PM, Ken Tabb wrote: My questions are: [1] Presuming that my Employee objects all have permanent objectIDs, can I rely upon using myEmployee] obje

Re: Using Core Data ManagedObjectIDs to uniquely name files

ly my fault if it isn't working, rather than trying to figure out if the Core Data objectID naming system has changed between versions! Thanks for your help, Ken On 6 Apr 2010, at 4:17, Sean McBride wrote: On Tue, 6 Apr 2010 12:27:18 +0100, Ken Tabb said: I have a Snow Leopard no

Using Core Data ManagedObjectIDs to uniquely name files

a development release XML store), but I just want to check if I'm making safe assumptions as it feels almost as dirty and sneaky as playing with private APIs, and I'd rather not base a shipping app on something just because it happens to work right now for me on my machine :) As eve

Re: Core Data: Custom to-many relationship setter not being invoked

hing I need via KVO, but I couldn't see what I was doing wrong, so presumed I was misunderstanding it (a common cause, you'll be surprised to hear). Thanks folks, Ken Tail between his legs again... . . . . . . . . . . . . . . . . . . . . . . . . . . . Dr. Ken Tabb Mac & UNIX progra

Re: Core Data: Custom to-many relationship setter not being invoked

#x27;s relevant, but the Department's 'employees' relationship >> is mandatory, as is the inverse relationship. > > No, it's not relevant -- such validation requirements are checked only when > the Core Data store

Re: Core Data: Custom to-many relationship setter not being invoked

I edit them to - addEmployeeObject / -addEmployee (singular), they also don't get called. Fire the lot of them I say, they're causing me too much aggro ;) Ken On 23 Feb 2010, at 4:05, Jeffrey Oleander wrote: It's not something simple like Employees vs. Employee is it? -

Re: Core Data: Custom to-many relationship setter not being invoked

'employees' relationship is mandatory, as is the inverse relationship. Weird isn't it :) Ken On 23 Feb 2010, at 2:34, Quincey Morris wrote: On Feb 22, 2010, at 15:54, Ken Tabb wrote: Yep I implemented all 4, as per the Design -> Data Model -> Copy to clipboard

Re: Core Data: Custom to-many relationship setter not being invoked

both the add *and* remove? The framework might require both to assume compliance. HTH, Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" - - - - - - - - - - Dr. Ken Tabb Mac & UNIX Developer - Health & Human Sciences Machine Vision & Neural

Re: Core Data: Custom to-many relationship setter not being invoked

Department / Employee analogy is breaking down here!). Thanks again for the info, I'll meanwhile file a bug about the 10.6 documentation. Cheers, Ken On 22 Feb 2010, at 11:21, Jerry Krinock wrote: On 2010 Feb 22, at 14:59, Ken Tabb wrote: My problem is that Department's custom -

Core Data: Custom to-many relationship setter not being invoked

in the face... Thanks in advance for any "you stupid idiot you need to do this, man" replies :) Cheers, Ken . . . . . . . . . . . . . . . . . . . . . . . . . . . Dr. Ken Tabb Mac & UNIX programmer Neural network & computer vision researcher University of Hertfordshire, UK __

Re: MVC design Q - remembering Core Data selections

uld be a job for user defaults. So at app shut down, I'd just intervene at that point and write the current selection details to user defaults. No need to futz with your model. Of course, you'd only then have the selection for one of the companies, but that is sort of what Mail d

Re: MVC design Q - remembering Core Data selections

(i.e. new) to permanent (i.e. saved) though? Or should I only write the file / 2nd store when the app is quitting (after everything that's staying has been committed)? Hope I've stated my problem well enough - if anything needs clarification let me know. Thanks in advance for any help

MVC design Q - remembering Core Data selections

n session 1, I listen to: - Playlist 5, track 150 followed by: - Playlist 12, track 27 ... then hopefully in session 2, it would remember that last time I launched this app, I was last listening to: - Playlist 12, track 27 ... but I'd also like that, were I to switch to Playlist

Simple Core Data problem - zombie objects left in store

) Thanks in advance for pointing out my stupidity, Ken p.s. I've checked and the app delegate is definitely using NSXMLStoreType, not NSCryogeneticStoreType ;) - - - - - - - - - - Dr. Ken Tabb Mac & UNIX Developer - Health & Human Sciences Machine Vision & Neural Network r

Version number objects

ll who celebrate it, and thanks in advance for any help you can give, Ken - - - - - - - - - - Dr. Ken Tabb Mac & UNIX Developer - Health & Human Sciences Machine Vision & Neural Network researcher - School of Computer Science University of Hertfordshire, UK

Core Data "Save as" versions

find, so apologies if I've missed the obvious. Thanks in advance for any light you can shed, Ken - - - - - - - - - - Dr. Ken Tabb Mac & UNIX Developer - Health & Human Sciences Machine Vision & Neural Network researcher - School of Computer Science University of Hertfordshi