SwiftUI List performance

It's peculiar that a reinstall didn't fix that.First try correctly setting the catalog using the following command in Terminal (the whole thing, including the text that appears as a link):sudo softwareupdate --set-catalog https://swscan.apple.com/content/catalogs/others/index-10.11seed-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gzAlso, have you tried booting into Safe Mode, or booting normally but creating a new temporary admin account and updating from there?Follow these steps to start up into safe mode.Start or restart your Mac.Immediately after you hear the startup sound, press and hold the Shift key.Release the Shift key when you see the Apple logo appear on the screen.After the Apple logo appears, it might take longer than usual to reach the login screen or your desktop. This is because your Mac performs a directory check of your startup disk as part of safe mode.If you're not sure if your Mac is started in safe mode, you can use System Information to check this. T

in the top line it say viewcontroller4 does not confirm to protocol: SKPaymentTransactionObserverCan you help:This is my code:/ / / / / / / import UIKit import iAd import StoreKit class ViewController4: UIViewController, ADBannerViewDelegate, SKPaymentTransactionObserver, SKProductsRequestDelegate { class Test: NSObject, SKPaymentTransactionObserver { func paymentQueue(queue: SKPaymentQueue!, updatedTransactions transactions: [AnyObject]!) {} func attemptAddingSelfAsObserver() { SKPaymentQueue.defaultQueue().addTransactionObserver(self) } } @IBOutlet var s1: UIButton! @IBOutlet var s2: UIButton! @IBOutlet var s3: UIButton! @IBOutlet var more: UIButton! @IBOutlet var info: UIButton! @IBOutlet var home: UIButton! @IBOutlet var banner: ADBannerView! @IBOutlet var restore: UIButton! @IBOutlet var skipsl: UILabel! var moreon = 1 func updatelbl() { if infinite == off { skipsl.text = Skips = (skips) } else if infinite == on { skipsl.text = Skips = Infinite } } func morefunc() { if moreon == 1 { s1.setTitle(22 skips

Based on all the items listed above, I believe you are going to have to write some custom code. 🙂For others reading, the original post is referring to WWDC 2014 video titled A Look Inside Presentation Controllers in https://developer.apple.com/videos/wwdc/2014/Maybe you could suggest that Ray Wenderlich and the gang update the following tutorial to use UIPresentationController: http://www.raywenderlich.com/78568/create-slide-out-navigation-panel-swift Ray's Twitter is @rwenderlich and his team's twitter list is https://twitter.com/rwenderlich/lists/raywenderlich-com-teamAn additional option is to download the sample code from WWDC 2014 and play around with it a bit to get a feel for what would be involved: https://developer.apple.com/library/ios/samplecode/LookInside/Introduction/Intro.html

I think I now found out what the limits for data transfer are by watching a session recording from the WWDC 2015 (https://developer.apple.com/videos/wwdc/2015/?id=704). There they said that the 2 GB is only for assets and the 40 requets per seconds which are also listed on the CloudKit Website are only for databases. So Apple does not count the bytes you are down - or uploading to your public databases, they count only the requests per second to your public databases.

There are a lot of cases where you don't carewhat the error is, and what's important is whether the file is reachable or whether you can perform some operation or not.Here's a couple more, in addition to the ones already mentioned:- Setting the color of a view object representing a file in the project, dependent on whether the file is reachable or not. For something like Xcode's left-hand sidebar, does it matter if the file is unreachable because it's missing, or because you don't have read permission to its parent folder? Not really, you just want to color it red to show that you can't open it.- Closing and/or releasing some kind of resource, whether it's a file descriptor, a network socket, or whatever. Like the temp files, it'll be closed when your app exits anyway, and its failure to close won't affect your processing of whatever data you just read from it without errors.- Implementing a delegate method, or overriding a method, or doing something with a method whose signature looks something like

Maybe I am misunderstanding you but I do not get how you come to the conclusion that generics are compiletime only.I know in Java for example there is type erasure so you can not do something likeif(myObj instanceof List<String>) { /**/ }because the type parameter <String> is absolutely not available at runtime but this is NOT the case in swift.Take a look at the following:struct MyGeneric<T> { let val : T } let a = MyGeneric(val: hello) let b = MyGeneric(val: 42) func printType(arg: Any) { print(arg.dynamicType) } // prints the full parameterized type correctly: printType(a) /* MyGeneric<Swift.String> */ printType(b) /* MyGeneric<Swift.Int> */ func isStringGeneric(gen : Any) -> Bool { return gen.dynamicType == MyGeneric<String>.self } // compared the the type correctly print(isStringGeneric(a)) /* true */ print(isStringGeneric(b)) /* false */ func dynamicConstructor(gen : Any) -> Any? { if let t = gen.dynamicType as? MyGeneric<String>.Type { return t.i

You mention advancing. What is the advancement?I believe that the entity/component model is solving the same problem that default protocol implementations are, and each is currently helpful only because neither addresses the root problem: that one must be able to see itself as multiple things at the same time. The play that you perform, as a guitarist, is not the same play that you perform, as a person pretending to be a cat, for example. Segmenting oneself into components that comprise the whole, and only allowing one implementation of a method, do no allow addressing oneself as a entity who does the same thing in different ways.