DTiPhoneSimulatorErrorDomain Code 2

> Is this possible now ? Planned for future Swift 2.x version ?I hope so - I was just trying to do exactly that, too.For the moment I worked around it by using separate getXXX and setXXX methods instead of having a computed property. But that's not ideal

Using the OSX Cisco VPN without issue.Photoshop CS6, Lightroom 5, Office 2011 and 2015, Sublime Text 3, Atom, Codekit 2, GitTower 2, all work fine.New Messages, Mail, iOffice apps fine.

Ugh, not good. I'll have to update two apps.

Found a solution that worked for me:Yes. First, download gdisk (URL in the OP) and run the installer package. Then run gdisk from a terminal window and run the v (verify command). If verify indicates no problems, then you're good to go and can just type q to quit. However, if it shows something like this, then you have the problem:sudo gdisk /dev/disk0Command (? for help): vWarning! Mismatched GPT and MBR partition! MBR partition 4, of type 0x07, has no corresponding GPT partition! You may continue, but this condition might cause data loss in the future!Identified 1 problems!Next, display the MBR partition table and make note of the start and end sectors for your BOOTCAMP partition. This should be partition 4 unless you've added additional partition(s), which is not officially supported by Boot Camp. It should show something like this:Command (? for help): rRecovery/transformation command (? for help): oDisk size is 1953525168 sectors (931.5 GiB)MBR disk identifier: 0x7C170CB2MBR partitions:Number Boot Start

Found a solution that worked for me:Yes. First, download gdisk (URL in the OP) and run the installer package. Then run gdisk from a terminal window and run the v (verify command). If verify indicates no problems, then you're good to go and can just type q to quit. However, if it shows something like this, then you have the problem:sudo gdisk /dev/disk0Command (? for help): vWarning! Mismatched GPT and MBR partition! MBR partition 4, of type 0x07, has no corresponding GPT partition! You may continue, but this condition might cause data loss in the future!Identified 1 problems!Next, display the MBR partition table and make note of the start and end sectors for your BOOTCAMP partition. This should be partition 4 unless you've added additional partition(s), which is not officially supported by Boot Camp. It should show something like this:Command (? for help): rRecovery/transformation command (? for help): oDisk size is 1953525168 sectors (931.5 GiB)MBR disk identifier: 0x7C170CB2MBR partitions:Number Boot Start

Here's the working code: let bundle = NSBundle.mainBundle() let path = bundle.pathForResource(Model, ofType: obj) let url = NSURL(fileURLWithPath: path!) let asset = MDLAsset(URL: url) let scene = SCNScene(MDLAsset: asset)Step 1) Get the path of the model fileStep 2) Load the file into a MDLAssetStep 3) Create a SCNScene with the asset (alternatively you can find the model inside the asset and add it to an existing scene)

Seems like 🙂. But as the data is still there I hope we'll get the 2 days back on a future release 😉

Apple is a user, just like us, when it comes to their contractor supplied forum software, which is typically from JIVE Software (Portland). JIVE tends to supply for Windows and open source, so when it comes to migrating anything, that's another checkbox on the option li$t. Witness the old forums now archived and locked. That option is carries the least overhead and co$t, after all.Migrating comments with intact threads from one format to another is rarely trivial/pretty, especially when the source is old and the new format is yet again proprietary. Migrating users is same only different.And since the old rep counter was broken...good riddance, I say. I've lost track of how many times I've seen counters restart for various Apple forums, so it's just another day online for me.The drivers for new forum software never included much value from old threads which primarily dealt with outdated code, tools, diluted/duplicate threads, etc. I suspect emphasis was placed on search, where users are nudged to do t

When you mention the line below, do you mean the following.You should define a property or method on the destination VC that says here is the data to be displayed.When the delegate call back method is called, I am currently writing the line of code below.self.feedViewController!.feedsTableView.reloadData()Since this is reloading a tableView in another VC you mentioned this was not ideal. Instead, would the following logic make more sense.In the home VC I would instead write.self.feedViewController!.updateTableView()Then in the FeedVC where the tableView resides I would perform the following in the updateTableView() method.func updateTableView() { self.feedsTableView!.reloadData() }I hope this is clear. Take care,Jon