column

Me too, and today they answered:We've made some updates to Sales reports to now show redownloads, and information on the device used. Additionally, there are some changes to Product Identifiers to support tvOS.The new device column shows where your app was purchased, updated, or redownloaded. Values include Apple TV, iPad, iPhone, iPod touch, and Desktop.The supported platforms column denotes which platforms your app supports. Values include iOS, tvOS, or iOS and tvOS.We also added redownloads to your reports. These are indicated by new Product Type Identifiers:3: Redownload of iPhone-only, or iOS and tvOS app (excluding iPad-only)3F: Redownload of Universal app (excluding tvOS)3T: Redownload of iPad-only appF3: Redownload of Mac app

You're basically holding a discussion with yourself here, but - you only ever directly download & install XCode from the one and only verified source there is: Apple.If you did download your copy from Apple, there isn't any reason not to follow through with the installation.The items disappearing from the Utility pane - I've had that since seemingly ever. It is irritating, but always remedied easily by switching between open files or at worst restearting XCode.Your other issues are hard to follow, given you mix them all up over various posts.Things persisting in test apps where they shouldn't are usually avoided by:- Clean Project- Clean Build Folder- Clear the content of the Derived Data FolderAlso if you've downloaded XCode and it only has 344kb then you know you haven't downloaded XCode.Last but not least - are your added subviews deleted in Interface Builder or are not not visible?My guess is - not visible (which basically is the thread where you came from).So - are they visible in the document outlin

What do you mean by columns? Do you mean the text in the section headers? If that's what you mean you could make your own custom section headers that positioned their content a certain way and then make your cells do the same. Anyway, I don't think you can create constraints from anything inside a cell to anything outside the cell, at least I don't think it would work.

But I didn't use it to position the contents of the cell; only to position something else not part of the table view such that it pointed to the cell.>>> Yes, this is what I meant by columns. My header labels are not part of the table view, they are positioned above. And I want to position them relative to the content of the cell, which uses Auto Layout to adapt to different screen sizes. So, my question is Can I create programmatically NSLayoutConstraint instances between these labels and some content in my cell ?. I can't believe no one else has the same problem...

Matrix components are constructed and consumed in column-major order.https://developer.apple.com/library/ios/documentation/Metal/Reference/MetalShadingLanguageGuide/data-types/data-types.htmlThe reason that the results are not consistent with your expectations is that you are not constructing your matrix in column major order. Here's the matrix you're making:0 | 4 | 8 | 121 | 5 | 9 | 132 | 6 | 10 | 143 | 7 | 11 | 15

Thanks,I can't believe apple make it column-major order with out clearly specifying it,or it is a standard only I get confused?

That quotation is from the documentation. That was clear enough for me, but you can file a documentation bug if you have an idea about where they could put it which could educate people who are wired like you.As for standards, I come from Unity and don't know the CPU APIs well, but I worked a lot with Cg, which was row-major, and GLSL, which was column-major. Neither option is good, for readability. Named subscripts would be better. However, I don't think that we could do that without a speed decrease. As such, Xcode should be the one to diagram this for us, not documentation or a forum.

I would recommend trying to use the same relationships to position your column headers and the views in the cells. Have a view that is the same width as the tableview. The column headers would be subviews of that view. The positions of the column header views would be relative to the container view. Set up the cells to use the same relationships relative to the cell content view.