MSFUiDispatcher

Objective-C


@interface MSFUiDispatcher : NSObject {
  void *swigCPtr;
  BOOL swigCMemOwn;
}

Swift

class MSFUiDispatcher : NSObject

How the facade reaches an app’s UI thread.

A subscription that asked for UI delivery is queued rather than run where the event was produced, and this is what wakes the queue: post() is called from the producing thread and must arrange for MassifApi::drain to run on the UI thread.

Without one, UI subscriptions run INLINE on whatever thread produced the event and the facade says so once - delivering on the wrong thread beats dropping the event, but it is not what the subscription asked for.

  • Called from the producing thread. Get onto the UI thread and call MassifApi::drain. May be called again before a previous drain has run; one drain empties the whole queue.

    Declaration

    Objective-C

    - (void)post;

    Swift

    func post()

  • Called from the producing thread. Get onto the UI thread and call MassifApi::drain. May be called again before a previous drain has run; one drain empties the whole queue.

    Declaration

    Objective-C

    - (void)postSwigExplicitMSFUiDispatcher;

    Swift

    func postSwigExplicitMSFUiDispatcher()

  • Undocumented

    Declaration

    Objective-C

    -(id)init;

    Swift

    init!()

  • Undocumented

    Declaration

    Objective-C

    -(void)dealloc;

    Swift

    func dealloc()