Package com.digi.wva.async

Callbacks on UI thread

See: Description

Class Summary

Class	Description
EventChannelStateListener	Listener for certain events that happen within the EventChannel class, such as successfully connecting, stopping because of an error, and the remote end of the socket closing.
EventFactory	Container for static factory function EventFactory.fromTCP(org.json.JSONObject) and common event enumeration(s).
FaultCodeCommon	Provides a collection of static content and methods pertaining to fault codes.
FaultCodeEvent	Encapsulation of an event containing fault code data.
FaultCodeListener	Provides a callback for handling new fault code information.
FaultCodeResponse	FaultCodeResponse objects encapsulate fault code data.
VehicleDataEvent	Encapsulation of an event containing vehicle data.
VehicleDataListener	Provides a callback for handling new vehicle data.
VehicleDataResponse	VehicleDataResponse objects encapsulate vehicle data.
WvaCallback<T>	Callback class used to receive response information from asynchronous calls into the library.

Enum Summary

Enum	Description
AlarmType	Enumeration of the different alarm types supported by the WVA.
EventFactory.Type	Enumeration of the general types of events that can be sent by the WVA.
FaultCodeCommon.Bus	Enumeration of the different CAN buses exposed by the WVA.
FaultCodeCommon.FaultCodeType	Enumeration of the different fault code message types.

Package com.digi.wva.async Description

Callbacks on UI thread

To ease use of the WVA Android library, all asynchronous methods in the WVA class will by default execute their callbacks on the application UI thread (or main thread). Additionally, any "listeners" used to subscribe for data or alarms, or TCP stream connection status, will also have methods executed on the main thread by default.

See the documentation for the following methods for more information on this functionality, and how to force callbacks to execute in a background thread instead, if this is useful for your application:

• WvaCallback.runsOnUiThread
• EventChannelStateListener.runsOnUiThread
• VehicleDataListener .runsOnUiThread
• FaultCodeListener .runsOnUiThread

These are some of the interactions which must be run from the main thread in Android:

• Interacting with or updating views (such as changing text, changing icons, calling notifyDataSetChanged() on an adapter, etc.)
• Creating new Toast notifications
• Manually drawing/painting on screen

The following tasks should not be done on the UI thread:

• Loading data from the network
• Performing long-running calculations
• Accessing a file or database

If the UI thread is blocked for more than a few seconds, the user may encounter an "application not responding" dialog. You should make sure to be careful in deciding which callbacks and listeners should be executed on the UI thread, and which can be handled on a background thread. (You always have the option of posting a Runnable to the main thread yourself.)