home.social

#selector — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #selector, aggregated by home.social.

  1. Vous êtes du genre "Saint Valentin" ?
    J'ai la bande son qu'il vous faut !
    Ce mardi 11 février à 21h sur rigfm.fr/,
    ou sinon sur soundcloud.com/pomponf...
    #selector #mix #frenchtouch #love #slow

  2. @[email protected] @y2mango `UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)` is how to do it. Allowed seemingly on the App Store as I've done it in HomeRun 2 for a few years

  3. @[email protected] @y2mango `UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)` is how to do it. Allowed seemingly on the App Store as I've done it in HomeRun 2 for a few years

  4. @[email protected] @y2mango `UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)` is how to do it. Allowed seemingly on the App Store as I've done it in HomeRun 2 for a few years

  5. @[email protected] @y2mango `UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)` is how to do it. Allowed seemingly on the App Store as I've done it in HomeRun 2 for a few years

  6. @[email protected] @y2mango `UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)` is how to do it. Allowed seemingly on the App Store as I've done it in HomeRun 2 for a few years

  7. @jamesthomson amusingly you can do that on the App Store without issue.

    A lot of apps used to/still do it to close their apps after a widget action.

    UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)

  8. @jamesthomson amusingly you can do that on the App Store without issue.

    A lot of apps used to/still do it to close their apps after a widget action.

    UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)

  9. @jamesthomson amusingly you can do that on the App Store without issue.

    A lot of apps used to/still do it to close their apps after a widget action.

    UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)

  10. @jamesthomson amusingly you can do that on the App Store without issue.

    A lot of apps used to/still do it to close their apps after a widget action.

    UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)

  11. @jamesthomson amusingly you can do that on the App Store without issue.

    A lot of apps used to/still do it to close their apps after a widget action.

    UIControl().sendAction(#selector(URLSessionTask.suspend), to: UIApplication.shared, for: nil)

  12. Again I run into this.

    E.g.

    super.responds(to: #selector(cancelOperation(_:)))

    in an NSCollectionViewItem *subclass* that requires an `override` declaration does return `true`, but actually forwarding

    super.cancelOperation(sender)

    produces a runtime 'warning' about unrecognized selector.

    This happens to me from time to time with AppKit subclasses, and I document "no need to call super because..." usually.

    But I still haven't really grasped the reasons here.

  13. Again I run into this.

    E.g.

    super.responds(to: #selector(cancelOperation(_:)))

    in an NSCollectionViewItem *subclass* that requires an `override` declaration does return `true`, but actually forwarding

    super.cancelOperation(sender)

    produces a runtime 'warning' about unrecognized selector.

    This happens to me from time to time with AppKit subclasses, and I document "no need to call super because..." usually.

    But I still haven't really grasped the reasons here.

  14. Again I run into this.

    E.g.

    super.responds(to: #selector(cancelOperation(_:)))

    in an NSCollectionViewItem *subclass* that requires an `override` declaration does return `true`, but actually forwarding

    super.cancelOperation(sender)

    produces a runtime 'warning' about unrecognized selector.

    This happens to me from time to time with AppKit subclasses, and I document "no need to call super because..." usually.

    But I still haven't really grasped the reasons here.

  15. Again I run into this.

    E.g.

    super.responds(to: #selector(cancelOperation(_:)))

    in an NSCollectionViewItem *subclass* that requires an `override` declaration does return `true`, but actually forwarding

    super.cancelOperation(sender)

    produces a runtime 'warning' about unrecognized selector.

    This happens to me from time to time with AppKit subclasses, and I document "no need to call super because..." usually.

    But I still haven't really grasped the reasons here.

  16. Again I run into this.

    E.g.

    super.responds(to: #selector(cancelOperation(_:)))

    in an NSCollectionViewItem *subclass* that requires an `override` declaration does return `true`, but actually forwarding

    super.cancelOperation(sender)

    produces a runtime 'warning' about unrecognized selector.

    This happens to me from time to time with AppKit subclasses, and I document "no need to call super because..." usually.

    But I still haven't really grasped the reasons here.