Welcome to the Harris Geospatial product documentation center. Here you will find reference guides, help documents, and product libraries.


Harris Geospatial / Docs Center / Using IDL / Information Skipped During Export

IDL

Information Skipped During Export

Information Skipped During Export

The Assistant skips certain information when creating an object specification for exporting because such information is unnecessary or unavailable for a wrapper object.

Lifecycle Methods


The lifecycle methods of the IDL source object, Init and Cleanup, are not presented in the list of methods to export in the Assistant. These methods are called through the bridge when the wrapper object stock methods createObject and destroyObject are called. (Note that Java capitalization is used here, COM names are different.) It is not useful to export a wrapper method explicitly for either of these routines.

For information on the stock methods, see Stock COM Wrapper Methods and Stock Java Wrapper Methods.

Get Property and Set Property Methods


The GetProperty and SetProperty methods of the IDL source object are not presented in the list of methods to export in the Assistant. These methods will be called through the Export Bridge when the wrapper object routines for setting or retrieving a specific property are called. It is not useful to export a wrapper method explicitly for either of these routines.

Drawable Object Event Handlers


For drawable objects (objects subclassed from IDLitWindow, IDLgrWindow, or IDLitDirectWindow) as well as IDLitDirectWindow superclass itself, the following methods are not typically needed in the exported object:

  • OnEnter
  • OnExit
  • OnExpose
  • OnKeyboard
  • OnMouseDown
  • OnMouseMotion
  • OnMouseUp
  • OnResize

By default these methods are not presented in the Assistant for export from either the original IDL source object or its superclasses.

These routines in the source object are called directly by the Export Bridge when events are being handled, and so they are typically not needed in the exported object.

Exporting these routines would be unnecessary and confusing to most users since they might assume that the methods in the exported object would be called, but under default conditions they are unused. The sophisticated user might actually want to call these in the client application, however, and so they can be presented in the assistant by starting the application with the DRAWABLE_EVENTHANDLERS keyword set (in addition to the OBJECT_FILE keyword). See Running the Assistant for details.

Typically, the methods found in .pro code object definition files will appear in the Export Bridge Assistant. Since IDLgrWindow and IDLitWindow object definition files are built-in, they do not appear as superclasses and their methods are not presented in the Assistant.



© 2017 Exelis Visual Information Solutions, Inc. |  Legal
My Account    |    Buy    |    Contact Us