Magic Cube

  public interface Updatee

    {

    void receiveUpdate(RubikUpdates update);

    void errorUpdate();

    }

  private static final int DEBUG_NOT_YET = 0;

  private static final int DEBUG_RUNNING = 1;

  private static final int DEBUG_SUCCESS = 2;

  private static final int DEBUG_FAILURE = 3;

  private static Updatee mUpdatee;

  private static String mSuspicious;

  private static int mDebugState;

      if( mUpdatee!=null ) mUpdatee.receiveUpdate(mUpdates);

      mDebugState = DEBUG_SUCCESS;

      if( mUpdatee!=null ) mUpdatee.errorUpdate();

      mDebugState = DEBUG_FAILURE;

    String suspicious = URLencode(mSuspicious);

    url += "?i="+deviceID+"&d="+suspicious;

    mDebugState = DEBUG_RUNNING;

  public void suspicious(AppCompatActivity act, String suspicious)

    mSuspicious = suspicious;

///////////////////////////////////////////////////////////////////////////////////////////////////

// Yes it can happen that the second Updatee registers before we sent an update to the first one

// and, as a result, the update never gets sent to the first one. This is not a problem (now, when

// there are only two updatees - the RubikStatePlay and the UpdateDialog)

//

// Yes, there is also a remote possibility that the two threads executing this function and executing

// the sendDebug() get swapped exactly in unlucky moment and the update never gets to the updatee.

// We don't care about such remote possibility, then the app simply would signal that there are no

// updates available.

  public void signUpForUpdates(Updatee updatee)

    {

         if( mDebugState==DEBUG_SUCCESS ) updatee.receiveUpdate(mUpdates);

    else if( mDebugState==DEBUG_FAILURE ) updatee.errorUpdate();

    else mUpdatee = updatee;

    }