smb big sur

It is more useful to post actual code declarations and copied and pasted error messages, not your summary of how you think it is 🙂 Such problems are often rooted in incorrect assumptions about what error messages mean etc.I would split those big long lines into multiple statements so you can more clearly see what's happening, and step through it in the debugger, checking each step individually.NSInteger tag = [sender tag]; // Is this the value you expect? UIView *view = [self.view viewWithTag:tag]; // Is this view non-null and an instance of UITextField? NSString *text = ((UITextField *)view).text; // Is this non-null?But your use of sender makes me wonder. That sounds like a parameter to an IBAction, perhaps coming from a button. If that button's tag property is 3, and the text field you are looking for also has a tag of 3, then perhaps viewWithTag is returning the button. But all this is speculation since you haven't posted enough code. There are ways around that if that's the issue.

Swift 2 has not very many big changes. The biggest is the much wished for new error handling that requiers some rewriting of error handling code.

Hi Josh,Sorry about the delay i have been holidaying in the big apple! Im back now though and am intending to try this tomorrow evening. It does look rather complicated and i dont fully understand what you mean as im not sure on what the storyboard does and what each of the components do yet.. ill amend the code fromvar skView:SKView = self.view as! SKView skView.showsFPS = false skView.showsNodeCount = false var scene:SKScene = GameTitles(size: skView.bounds.size) scene.scaleMode = SKSceneScaleMode.AspectFillto:var skView:SKView = self.gameView as! SKView skView.showsFPS = false skView.showsNodeCount = false var scene:SKScene = GameTitles(size: skView.bounds.size) scene.scaleMode = SKSceneScaleMode.AspectFilland see if that does the trick? As i said I havent used the storyboard so unsure what to do there, i havent studied about that yet i went straight into code as its what i know but if you have an explaination of what it is id be glad to hear it! I have a huge passion but no experience and no one

You can set the view controller's size to Freeform under simulated metrics, then make it as big as you want. I do this often if I am laying out content in a scroll view.

I think you have probably found a bug. I would expect it to work. It might be a bug that is a fring case, using Objective-C RTTI within Swift, and therefore it might not be a high priority fix 😟.Can you use this as a work around?protocol ABCProtocol { func abc() -> String } protocol XYZABCProtocol: ABCProtocol { func xyz() -> String } class BigData: XYZABCProtocol { func xyz() -> String { return XYZABC } func abc() -> String { return ABC } } func test(abc: ABCProtocol) -> String { if let xyzabc = abc as? XYZABCProtocol { return xyzabc.xyz() } else { return abc.abc() } } let big = BigData() test(big) // XYZABC

Dear PBK,Our plan was first to make the registration optional. But later as i said for cross platform issues , we coded it just to enter a username / password before buying a subscription. This doesn't make anybody to provide me a personal info. It is just a username and password For the sake of the customer so if he/she wants , she can use it on other devices. I dont understand why this is a big deal . YES , If I had wanted a personal info like birthday, email or anything else , you are right. this means that i am forcing people to enter private info to make the app function. But it is not true. I just make them create a username and password to use the app anywhere they want. This is not against rule 17.2 because i am not rquesting any special info. Other than this , without subscription, there is an inapp purchase for users to reach subscription content, so EVEN if they dont want to register, they can use the option. Please correct me if i am wrong at any of this ?. BTW, i couldnt get an answer fr

According Mad Catz (as stated in your link), the controller isn't licensed to support Mac OS X. The Steelseries Stratus XL is specifically marketed as having Mac OS X support, so I assume they have both an OS X and an iOS license for that controller.The Stratus XL is usable through the GameController framework in OS X (I can easily test by compiling and running Apple's DemoBots sample code). It's also usable through Apple's low level IOKit HID APIs. Most games in OS X only try to use gamepads through the IOKit APIs – for example the popular SDL library doesn't support GameController.framework in OS X at the moment, but it does use IOKit HID APIs for joystick input, and Steam's Big Picture mode uses SDL – so my Stratus XL works in Steam's Big Picture mode.

The general rule is, if a user swipes an app away, it is taken as a signal that they don't want that app to be running in any form anymore, and the app will no longer be launched based on a background service.Region Monitoring is an exception to that, as in, your app will be relaunched even after user terminates it. Significant Location Change is not in this exception, and won't relaunch your app.It is hard to tell what is causing your app to not be relaunched without knowing more details. Assuming you have read the documentation and followed the steps correctly, here are some gotchas I can think of:- you mentioned GPS. Region Monitoring does not use GPS. It uses location data obtained via WiFi access points and mobile phone towers. To use GPS, your app must also be using the Standard Location Service (via startUpdatingLocations call). If you are indeed using that, once the app is terminated, you will no longer receive GPS updates and Region Monitoring will depend solely on alternative sources, which will sig

Agreed on all counts and I'm glad I found this post about the issue because I was about to start my own. For some bizarre reason after the release of iOS 9 and El Captian the pertinent forum pages for those OS's just disapeared under the BETA section of the forums. Not a big deal except Apple nearly instantly released iOS beta 9.1 and similar for osx 10.11+. Obviously the bug reporting function is most important but it was nice to see if other devs were dealing with any similar issues others might be having, workarounds etc. Oh well, strange!

>The process has changed a great deal since then, and there are fragments of the conflicting documentation, but nothing I have found that actually spells anything out.Being around so long now, this shouldn't be a surprise to you, I'd think - that and if things were going to change, they would have done so long ago. But yeah, what you said, especially from those of us that have been here since the beginning.For me, tho, it's been a steady tail-chase, a 'situation normal', where Apple makes some things easier, then others harder...change for change's sake - a routine from Apple that doesn't seem to have improved over time, with consistent disconnects that seem to fall on deaf ears from our POV. From cryptic docs to forums a gradeschool wouldn't care for, it all combines to make things harder for devs, like it's one big long test to weed out the weak. No wonder devs hold parties when an app finally gets into the store...For the dev tho, it's still build/provision app, then submit/wait & repeat as