smb big sur

2 hours would be a big improvement over the 3 days that I've been trying to upload my screenshots for so far!😟

Both of the large monitors connected to my mac are also TVs w/HDMI, so for now I can point/shot build/test/view, etc.I can move this ATV to the big screen in the living room if I have to, but I can see buying another at some point so I don't have to juggle.It would be nice to be able to wi-fi test, tho...

big S vs little s...Thanks Microsoft for raising me 'case unobservant for most things' in the computer industry...Took me a while to find it, 'ss' is for seconds with the fraction dropped 'SS.SSS' is for seconds with the fraction, out 3 places.. Still not understanding why the seconds are off, and why it swings wildly around....

Ditto here. The link to do that is just not present. No icon next to the build number. No link at the top of the version page. I've done this many times in the past and it is just gone. This seems like a big problem.

BTW - on a separate note, with Xcode 7.1 beta 3 (the one that just came out today), I import an xliff file that works under 7.01 - and it gets me to the window where I approve the import and then I get this error (radar 22997699):XLIFF target-language attribute missingBasically I'm just seeing XCode's localization tools go downhill big time since Xcode 7. It seems like every release does not fix any of the issues that I talked to you about at WWDC and introduces new ones. I can't tell you how disappointed and discouraging this is. I've put in so many bug reports only to see things get worse.I tell you, if you sat down with me for a few days and we ran through my project back and forth, you would fix so many issues.Console:10/6/15 2:59:51.695 PM Xcode[61177]: Failed to connect (comparisonSplitView) outlet from (DVTComparisonScrollCoordinator) to (DVTComparisonSplitView): missing setter or instance variable10/6/15 3:00:05.349 PM Xcode[61177]: [default] Failed to updated bookmark for item (null) [063E9D

Don't think it's related to Bitcode or language. Not there in English for me and not using Bitcode.Think it's just a plain old bug. They just deployed a big new UI. New UI has bugs. This one is just more critical than most.

I would suggest that you design your model API first. Whether the data is backed by core data, or pure sqlite, or a big in-memory array/dictionary should not matter, except in how the model is implemented.If you can decide on a reasonable model API, then how you implement the backend is an implementation detail of the model. This way you can use whatever backend technology you want, and change it easily enough if you find your requirements change.Since you referenced the OS X programming book, I assume this is for OS X, and unless your objects are incredibly huge, you can probably get away with having your model be completely resident in memory as 25,000 objects is not many at all. However, remember that loading and saving will take longer when you atomically load/save the whole model at once.Thus, design your model API to be independent of how the storage and retrieval is implemented, and start with the easiest backend implementation to do the job, knowing you can swap it out at any time.

In my opinion, the model should fully encapsulate the method of communication. So when iOS 11 rolls around and NSURLSession is deprecated for the Next Big Thing (TM) like NSURLConnection was 🙂 you don't have to change your controller too. That's just an opinion though. If it ends up with a bunch of boilerplate then it might not be ideal either.I think a delegate is fine between the model and controller *if* you will only ever have one entity interested in model changes. If there might be more than one delegate some day then you are looking at a custom delegate implementation more like a Java listener list (add / remove delegate methods, and the model keeps a list, not just a single delegate property) or the more common notifications or KVO.

Been stuck on processing for hours.How big is your code-base. Our app (Cybmal) is a pretty massive project so I am wondering if it's only affecting large projects due to some sort of code-analysis or something.

Obvious comman sense has abandoned me! I just need to split my code in viewDidLoad into separete methods. Lets just say the fatigue on being in a project too long, thats just the first project which turned out to be very big and wasn't well planned out of inexperience, is taking over me. I need to take a break.

I'm getting the exact same crash as Rick Fan under Xcode 7.0.1. I tried editing the accounts in the preferences, as TommieC suggested, but I just get a crash when I go to that tab in the preferences. It turns out that I can run the beta Xcode 7.1 without crashing, however. So I used 7.1 to clear out the accounts in the preferences. When I relaunched 7.0.1, it opened without any problems. I was able to add back the accounts and everything seems to be working.Thanks, Rick Fan for posting and TommieC for answering. Big help! I was hitting my head on the wall over this problem.

Hi, I was playing with the settings as well and without reading the posts above came to the same conclusion.Basically your Apple ID needs to be from a country that supports Siri.If you just change the region and your Apple ID is not from there, it signs you out of your account.But you can add (just like the gen2 & gen3) multiple apple id's and switch between them when relevant.PS. I am not sure who approved (I know i am stepping on big toes here) the keyboard on tvOS, but I can't wait to pair a bluetooth keyboard to it. I prefer the grid-keyboard big time. (rant over)