quellish

Los Angeles, CA

1h
comment Why static variable not pointing to nil after being once initialized?
@timpone sharedStore IS a local variable, and it is declared and initialized to nil. The code in the question will enter the conditional that creates it. You own code also demonstrates this: xyzzy is a static local variable declared and initialized to 0, which is what is printed on the function's first invocation.
1h
comment Does NSXMLParser work in today widget?
Please update your question with your NSXMLParserDelegate methods.
2h
comment Why static variable not pointing to nil after being once initialized?
Static variables have scope, and in this case the scope IS local. The value is remembered across invocations. Sandeep, sharedStore is scoped to be only available within that method. It's set to nil when it's declared and initialized. If you were to set it to nil on the line after initPrivate, yes, you would lose the address you just set on the initPrivate line.
2h
comment NSFetchedResultsController doesn't always call didChangeObject:atIndexPath:forChangeType:newIndexPath: for NSFetchedResultsChangeMove
What is causing the move? From your description, it sounds like the change is happening in the table view (i.e. the user is moving a row)
3h
comment Trying to implement Key-Value Observing for first time, get some error
Doesn't matter. His question is "How do I set the breakpoint to resolve this issue" not "Guess my intent and rearchitect my class". He obviously implemented the accessors to access a different property - not a straight copy and paste - and that's up to him. He may have good reason for doing so.
3h
comment Trying to implement Key-Value Observing for first time, get some error
He implements the KVC mutable ordered collections accessors for the key "data", which is fine. If an object calls [thing mutableArrayValueForKey:@"data"] it will get a mutable proxy object that will call into his KVC accessors, which will actually modify the addedLetters mutable array. There is nothing non conformant about his KVC accessors.
7h
comment Using managed object context with Dispatch queue in Core Data
@WarrenBurton take a look at gist.github.com/quellish/4f59680cc0a679a67128
7h
comment Using managed object context with Dispatch queue in Core Data
@WarrenBurton, nope. Set a local variable to person.firstname outside of your main queue dispatch block, and set self.myUIElement.text to that local variable inside the block. I can't illustrate this better in a comment.
7h
comment Trying To Group Core Data Fetch Results By Date
Your fetch request is telling Core Data to return each result as an NSDictionary. It is likely that some place you are trying to access a result as if it were an NSString, when it is an NSDictionary - probably to read a property value (i.e. you are assuming it returned some property as each item of the results) - likely 'weekBegin'.
7h
comment Memory Leakage While Trying to Blur a UIImage using Core Image
performSelectorInBackground:withObject: is somewhat notorious for making it easy to leak. This method creates a new thread and runs the selector on that thread. Some of the UIKit functionality you are using is not safe to use from any thread but the main thread, which is not good. However, to find your leak, post some information from Instruments such as a screenshot of a trace using the Leaks instrument.
8h
comment coredata: CoreDataGeneratedAccessors Generates NSSet to store multiple items
It's not clear from your question where the problem is. Is "Bed" an InventoryItem with the "name" of "Bed", or is it a specific instance of an InventoryItem managed object that you are adding twice? For what you appear to be trying to do, InventoryItem should probably be an abstract entity, with Bed, etc. being sub entities.
9h
comment Trying to implement Key-Value Observing for first time, get some error
Tom, if he puts the removal in both places it's likely to be removed twice, and result in an exception - one of the reasons doing KVO observation from inside an accessor is difficult.
9h
answered Error in a method prototype
13h
comment coredata: CoreDataGeneratedAccessors Generates NSSet to store multiple items
The NSSet is a relationship to other managed objects. The data the managed objects represent is not part of the criteria for uniqueness.
13h
comment iOS CoreData - Serialize entire object instead of creating Entity
Please update your question detailing what you feel is hard/difficult about this.
13h
revised When does NSManagedObject -managedObjectContext "return nil if the receiver has been deleted from its context"?
added 9 characters in body
1d
comment How to ensure data consistency and truly take advantage of Core Data?
I could give you the long version, but the short version is that often they're using Core Data as a local cache because they do not understand the protocols they are using. The URL loading system already supports offline access, and the HTTP protocol provides freshness which when used correctly on the server side ensures consistency. If the server side API is poorly designed, there isn't anything you can do on the client to solve it. Garbage in, garbage out.
1d
answered When does NSManagedObject -managedObjectContext "return nil if the receiver has been deleted from its context"?
1d
comment Access raw NSData for a Transformable attribute in Core Data
Why do you want to do this without using the value transformer? That is not clear from your question.
1d
comment CoreData obtainPermanentIDsForObjects crash with Xcode 6 Beta 6
This isn't an intended or supported use of obtainPermanentIDsForObjects. Save the context instead. In your code, get the user object and ID after the save, in the completion handler.
1 2 3 4 5