smb big sur

So I'm a big fan of the method indexOf() on CollectionType:extension CollectionType { func indexOf(@noescape predicate: (Self.Generator.Element) -> Bool) -> Self.Index? }It's really useful for finding the first item in a collection that satisfies the closure:let foo = 0...10 let firstItem = foo.indexOf { $0 > 5 }Sure it's O(n), but sometimes you don't care or that's acceptable behavior. Now I'd also really like to have a corresponding lastIndexOf method, which would return the last item in the collection that satisfies the closure. But this doesn't seem to fit well with CollectionType as it is, as I think SequenceType.Generator only goes forward. And I think maybe _Incrementable might be a part of this too? It appears to only index forward as well.Sure, I could always just do something this:let lastItem = (foo.count - 1) - foo.reverse.indexOf { $0 < 5 }But that seems like it would incur a performance penalty by reversing the array. What I really want is to actually iterate through the arr

Hello,SInce I use EL Capitan beta, I have to ask this here.Some applications (under /Applications), are greyed, and some I can open, I get this message:You do not have permission to open the application “BBEdit”.Contact your computer or network administrator for assistance.I know I can fix things as 'root' user, but I need an expert to tell me the correct commands to handle this.When I Get info for applications, some have ownership admin + everyone, with privilege 'No Access' .Some say 'Fetching...' , under the owner name.What should I do ?I think there should be a fix for the main root system, and another for my own admin user.I also included below the list of all my applications with ownership info. used command: ls -lHow can I fix all owner issues on my machine ?SincerelyDan------------------------------OS X EL Capitan10.11 Beta (15A243d)drwxrwxr-x 3 root admin 102 Jul 29 00:12 A Better Finder Rename 9.appdrwxrwxr-x@ 3 root admin 102 Jun 15 18:38 Acorn.appdrwxrwxr-x 3 root admin 102 Jul 9 23:08 Affinity Ph

Hi.Those of us using Cubase have found that the eLicenser doesn't work on public beta 4.Using the eLicenser app, we can get one poll for licenses working, but subsequent polls fail.Cubase fails to run at all.Also, the iLok dongle (for third party plug-ins) is failing.I've tried disabling SIP via command-R, but it still fails.A feedback report has gone in, but is anyone else struggling with this one?The previous betas were actually a big improvement over Yosemite for some audio devices...

Hello,First of all, let me thank you for your attention.I'm aiming to develop a big audiounit instrument for Apple computers, and my first question is about GUI and interaction with SWIFT. I would like to know if there's no counter-argument to develop the GUI using webkit, and if webkit is able to pass javascript callings to swift methods.I've already done some research on this case in the past, and found that earlier webkit versions could call objective-c methods using javascript.I'm willing to make a good quality, scalable (interface based on em unit and script modifying the font size on the window resize event) and responsive GUI using html and javascript, since i found this languages really appropriate to do this.Do Apple allow using of webkit in the case of audiounit development?thank you very much.best regards,Fabien

The biggest issue I have with Swift today is the lack of support for atomics. This is a particularly important issue because there's no workaround here, short of writing my code in Objective-C, but that can't interoperate with Swift value types or Swift generics (for the most part). The only partial workaround I have is the use of OSAtomic.h, for those cases where it actually provides the operation I need, but even that is risky because it's not actually guaranteed to be valid (because Swift operates on a writeback semantic model, there's no guarantee that e.g. calling OSAtomicCompareAndSwap32(value, newValue, &value) will actually behave as desired; Swift is free to make a local copy of the value, pass a pointer to that to the function, and then non-atomically write that back to the original location). And it often doesn't provide the operation I need anyway.Every single big Swift project I've done has run into this limitation. I usually end up working around it by giving up on the idea of atomi

I'm testing how many cells exists in collection view. I have following steps:1. Load collection view with 4 items and show them in small cell with smallCell reuse identifier2. Reload collection view with 2 items and show them in big cell with bigCell reuse identifier.After that XCUIApplication().collectionViews.count returns 6 elements (4 small cells and 2 big cells). Is this expected behavior? I would also like to know what elements are returned when calling XCUIElementQuery. Visible cells in collection view? I'm using Xcode 7 beta 5.