“SwiftData inheritance relationship”

We have a mostly C++ game that had no issues with Xcode 6. Ever since installing Xcode 7, I can't expand (or even view) certain variables that I could in Xcode 6.1. We have a std::string wrapper class (has-a relationship) and we cant expand the member variables to see what the UTF8 data of the std::string is. 2. We use polymorphism a lot and often have base class pointers in objects. Before in Xcode 6, we could see the derived type next to the memory address in Xcode debugger, as well as expand the derived class object to inspect its data. In Xcode 7, it doesn't show the derived type, nor can I expand to view the data. These 2 bugs effectively cripples our ability to debug our game!! We have to restort to printfs to debug - This is unacceptable.Surely other people have experienced a major bug like this?

As far as I can see, conforming to SequenceType is the only way to get a type to work with a for-in-loop.However, SequenceType adds a lot of stuff that doesn't necessarily make sense for every custom type we might want to use with a for-in-loop.(SequenceType's versions of map (always to an Array!), filter (to an Array!), sort (to an Array!) etc.)So why isn't there a much simpler protocol that specify/require only what is needed for the for-in-loop to work?(I guess such a protocol would require nothing more than a generate-method from its conforming types.And SequenceType would then of course inherit from that protocol.)

Hi everyone, thanks very much for reading, and thank you in advance for any light you can shed on this.The crash logs as CRASH: *** -[NSMutableSet unionSet:]: set argument is not an NSSet. UnionSet is being called as part of a fast enumeration. As you see below the thing I'm trying to loop over claims to be a _NSFaultingMutableSet. Here are a few more fun facts.This code is executing on a background thread using a NSManagedContext that is a child of the one from the main thread. I'm not new to core data threading, and this code has been in the wild for a while now and works for the rest of our users. The background (child) context is never saved, and we don't care about keeping up to date with changes on the main thread so we aren't doing anything like merging in changes from other contexts.self here is an instance of a Location, which is a subclass of NSManagedObject.self.settings is a toMany relationship with another NSManagedObject subclass.This is not the first odd thing core data has done to me

Hi! I had an old Core Data Entity, with relationship to AnotherEntity@property(nonatomic, retain) AnotherEntity *anotherEntity;In AnotherEntity.h a have an attribute@property(nonatomic, retain) NSString *title;I've modified some of Entity's attributes (added new one) so after generating new NSManagedObject subclass Xcode generated 4 new classes: Entity.h, Entity.m, Entity+CoreDataProperties.h and Entity+CoreDataProperties.mPreviously AnotherEntity.h had been imported in Entity.h, but this time Xcode imported it in Entity.m. So trying to access entity.anotherEntity.title gives me error Property 'title' cannot be found in forward class objectI've solved it, importing in Entity.h, but wonder if it's correct and Xcode was wrong importing in .m or it's me doing something wrong?

Hi,In a new swift story board project - i dragged and dropped collection view and tried to compile, but i am getting this errorUnknown segue relationshipAny idea?Screen Shot : https://www.dropbox.com/s/02z22eu5d88stm2/test.png?dl=0Project :https://www.dropbox.com/s/tyz0qecm7dk4o4x/test.zip?dl=0

I have subclasses of each of the following: a UIViewController managing a UICollectionView. The cells in the UICollectionView contain custom subclassess of UICollectionViewCell. I am populating it UICollectionViewCell subclasses from CoreData in - (UICollectionViewCell *)collectionView:(UICollectionView *)cv cellForItemAtIndexPath:(NSIndexPath *)indexPath and all this works fine and dandy. When the user selects a cell I pick this up in - (void)collectionView:(UICollectionView *)collectionView didSelectItemAtIndexPath:(NSIndexPath *)indexPath and segue off to process the selected cell. This all works fine and dandy.PROBLEM: I now want to have a checkbox on each of the UICollectionViewCells that the user can click to select the cell. After they have selected one or more cells I want them to press a UIButton on the top level UIView (managed by the UIViewController (that manages the UICollectionView) and I want a method in the UIViewController top process each of the selected cells one at a time. How do I communc

I have two tables in one view in kind of a master/slave relationship (not a SplitView). One, not filling the space will show the TableHeader just fine. The other, filled enough to scroll, refuses to show the header. Worse yet, when programmatically changing the focused cell, the animations to Top or Middle are squirrelly with inconsistent operation, sometimes putting the selected row partially out of the view.I'm probably going to abandon TableHeaders and install a Label above the table instead.BTW, focus and selection are two independent properties. In one table, I show selection by showing an icon arrow in the left of the cell -- a little more visual than the ghost selection indication. Selection occurs when clicked. In the other table, focus and selection work together. Selection in one of the tables advances focus/selection in the other table.

If I add a storyboard reference to the storyboard and then try to make that reference the target of a relationship segue from a tab bar controller, xcode always crashes immediately. Has anyone else had this problem? I know that ios8 doesn't support references as targets of relationship segues, but I'm explicitly targeting ios9 in the project's settings, and xcode shouldn't crash in any case.