Android™

Finalize Thread Pool

In some programming environments, such as VB6, FoxPro, and others (especially anything using the Chilkat ActiveX), it may be necessary to call FinalizeThreadPool just before your program exits. Otherwise a hard crash can happen. (This has only been known to happen in programs written in VB6, FoxPro, etc.) Android™

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    boolean success = false;

    // If your application made use of asynchronous Chilkat methods, which create background threads including a thread pool manager, 
    // then call FinalizeThreadPool just before your program exits.  This isn't required, but in some programming environments it 
    // prevents a crash on exit -- namely VB6, FoxPro, and other older programming languages where the ActiveX is used.
    CkGlobal glob = new CkGlobal();
    success = glob.FinalizeThreadPool();

  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}