“translate scheme”

We're getting a bit of topic here, but if you can't install and you can't restore, you could try booting into Single User Mode:Hold down Command and S keys at bootup for 10 secs or so. Wait until the command-line prompt appears (after all the text is done scrolling past.) Then type fsck -fy and press Return. Eventually, after five different checks that take varying amounts of time, you should get to one of two messages: The volume [your Mac's name] appears to be OK or FILE SYSTEM WAS MODIFIED. If you encounter the first message, type reboot and press Return. If you see the latter message, though, you'll want to run fsck -fy all over again. You can retype the command and hit Return, or press the Up arrow once and then press Return.If that doesn't work you can also erase your El Capitan partition in SUM and try again.Finally, if all else fails, you can restore to your original OS X with Internet Revovery mode:Boot to the Internet Recovery HD:Restart the computer and after the chime press and hold down the COMMA

Some boot problems can fixed by booting to the Recovery HD and using the utilities, some more can be fixed in Single User Mode.If you want to try one or both of those and need further help, let me know...Depending on your level of experience and enthusiasm though, it might be quicker (and should certainly be simpler) to just do a complete system restore as follows:Boot to the Internet Recovery by:Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.Partition and Format the hard drive: 1 Select Disk Utility from the main menu and click on the Continue button. 2 After DU loads select your newly installed hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window. 3 Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set

I think that's the question. Is there a compatibility behaviour, or does it not work at all. I guess the question is - if you add tagged assets in your asset catalogs for ODR, does Xcode 7 then complain if you set the deployment target < iOS 9?It would be easy enough to write app code that doesn't bother requesting the resources, and pretends they don't exist, if the NSBundleResourceRequest class is not available. We already do that kind of thing all over the place when supporting multiple OS versions. I am contemplating doing this in one app with an optional feature that takes ~60 MB of space. It would be nice if I could just add support for iOS 9 and later using ODR and not worry about implementing some home grown download scheme (or making the bundle 60 MB bigger unnecessarily).

In Xcode 7 beta 2, just using the == operator seems to work to compare meta-types in a playgroundprivate func translatorFor<T:Model>(type: T.Type) -> Translator? { for translator in translators { if translator.modelType == type { return translator } } return nil }

That does not seem to work. I get the error: `Binary operator '==' cannot be applied to two ObjectIdentifier operands`.Likely, this is because the types in question are generics conforming to a Protocol. While `Object` is a base class, Model is simply a Protocol. I want my model objects to have value semantics, so defining a base Protocol seemed the best way to transform a class type to a struct type. However, I checked and this actually works: private func translatorForObjectType<T:Object>(type: T.Type) -> Translator? { for translator in translators { if translator.objectType === type { return translator } } }So I can compare types when they're based on a class, but not when they're based on a protocol. I'm going to update my original post to reflect this.

UPDATE:I neglected to point out that `Model` is simply a protocol, and that seems to be the source of the problem. I cannot compare a generic type when it is based on a protocol. `Object` (from the framework I'm wrapping) is a class, so this works: private func translatorForObjectType<T:Object>(type: T.Type) -> Translator? { for translator in translators { if translator.objectType === type { return translator } } }The point of using a protocol was to allow me to convert `Object` objects into value-based structs (to be used by the rest of the app). Defining a protocol was the only way I could think to do that. Perhaps there's a better way? (Although I still want to avoid Classes for my Model)

Well, I don't know if I would recommend doing the following in production code, but I'm pretty sure it still worked back in 1.2...private func translatorFor<T:Model>(type: T.Type) -> Translator? { for translator in translators { if (translator.modelType) == (type) { return translator } } return nil }

Go to top left corner of the bar in Xcode 7.0 next to the play and stop symbol. You will see your project icon. Click there(set active scheme). This error can be caused by number of issues. In my case, they automatically delete my scheme for Watch App or Watch App Extension or equivalent. Manually added it and appropriately select the type of similator compatible to my scheme.P.S. Ascertain the WatchOS version is the one your app support via setting the Build Settings and your migration settings are properly adjusted. I recommend you google a sample code for WatchOS 2 project if that is the case.

Apple's sample code MetalDeferredLighting is pretty complex,it's not for beginners(since you metioned a cube casting shadow on a ground plane,I assumed you were looking for samples for beginners). I'm learning Metal too,what I'm doing is translating: 1.Take an OpenGL tutorial. 2.Learn the concept. 3.Do it again in Metal.Metal is a computer graphic API(just API,not a whole new concept).Metal's way of implementing a shadowmapping is exactly the same as OpenGL's except you're using a different API. sorry for my poor English,not a native speaker 😀