ewe.ui
Class WindowEvent

java.lang.Object
  extended byewe.ui.Event
      extended byewe.ui.WindowEvent

public class WindowEvent
extends Event


Field Summary
static int ACTIVATE
          This indicates that the window is now active.
static int APP_TO_FRONT
          This is a request from the VM for the application to bring itself to the front - displaying whatever it considers to be the current active window.
static int CLOSE
          This event is generated when either the close button for the window is pressed OR the system wants to close your application.
 Object data
          /** In the case of a DATA_DROPPED event this will hold data that has been dropped into the window.
static int DATA_DROPPED
          This event occurs when the user drops data picked up from another application or from the OS shell.
static int DEACTIVATE
          This indicates that the window is no longer active.
static int FLAG_CLOSE_BY_USER
          This bit is used as a flag to mApp.closeMobileApp() if the system knows for sure that the CLOSE event was generated by the user pressing one of the system close buttons.
static int HIBERNATE
          This indicates that the system (WinCE) wishes a Window to minimize its memory footprint.
 int x
          In the case of a DATA_DROPPED event this will be the x-coordinate where the data was dropped.
 int y
          In the case of a DATA_DROPPED event this will be the y-coordinate where the data was dropped.
 
Fields inherited from class ewe.ui.Event
consumed, events, flags, target, timeStamp, type, window
 
Constructor Summary
WindowEvent()
           
 
Methods inherited from class ewe.ui.Event
toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode
 

Field Detail

CLOSE

public static final int CLOSE
This event is generated when either the close button for the window is pressed OR the system wants to close your application. It is not possible to distinguish between the two - however a Close message sent by the system will always be directed to the mApp for your application. For mobile applications it is best to have a separate Exit button or function to allow the user to explicitly close the application, and then assume that any CLOSE message would therefore come from the system. Note that for WinCE applications it is assumed that the application will save its state somehow, so that the next time it runs it will continue from where it left off.

See Also:
Constant Field Values

ACTIVATE

public static final int ACTIVATE
This indicates that the window is now active.

See Also:
Constant Field Values

DEACTIVATE

public static final int DEACTIVATE
This indicates that the window is no longer active.

See Also:
Constant Field Values

HIBERNATE

public static final int HIBERNATE
This indicates that the system (WinCE) wishes a Window to minimize its memory footprint. This is usually called when you switch to a different application, AND may be called several times. It may be directed to any open window of your application.

See Also:
Constant Field Values

APP_TO_FRONT

public static final int APP_TO_FRONT
This is a request from the VM for the application to bring itself to the front - displaying whatever it considers to be the current active window.

See Also:
Constant Field Values

FLAG_CLOSE_BY_USER

public static final int FLAG_CLOSE_BY_USER
This bit is used as a flag to mApp.closeMobileApp() if the system knows for sure that the CLOSE event was generated by the user pressing one of the system close buttons. This currently only applies to the 'OK' button on WinCE. It is not possible to tell the difference between a close generated by the 'X' button or by the system on WinCE.

See Also:
Constant Field Values

DATA_DROPPED

public static final int DATA_DROPPED
This event occurs when the user drops data picked up from another application or from the OS shell. The data picked up is placed in the data member. That member will be either:

See Also:
Constant Field Values

x

public int x
In the case of a DATA_DROPPED event this will be the x-coordinate where the data was dropped.


y

public int y
In the case of a DATA_DROPPED event this will be the y-coordinate where the data was dropped.


data

public Object data
/** In the case of a DATA_DROPPED event this will hold data that has been dropped into the window. This will be either:

Constructor Detail

WindowEvent

public WindowEvent()