NSApp.currentEvent seems a bit over-optional when using Swift
| Originator: | neocool2 | ||
| Number: | rdar://20794942 | Date Originated: | 03-May-2015 11:41 PM |
| Status: | Open | Resolved: | |
| Product: | OS X SDK | Product Version: | 10.10 |
| Classification: | Other Bug | Reproducible: | Always |
Summary: NSApp.currentEvent needs to be unwrapped twice to get to the actual value. See <https://github.com/neonichu/XcodeRemote/blob/master/Code/AppDelegate.swift#L37> for an example. Steps to Reproduce: Use NSApp.currentEvent Expected Results: Unwrap it once to get to the actual value Actual Results: Unwrap it twice to get to the actual value Regression: - Notes: -
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!