Communication method among Views in Android system

Abstract

The invention provides a communication method among Views in an Android system. The communication method comprises the following steps: 1) defining a View message ID (Identity) corresponding to the View, and adopting a way that relevant data is attached to the View message ID to construct a View message; 2) constructing a corresponding Hash table of the View message and a View entity to realize the registration of the View message in the View, and logging off all View messages registered by the View in the Hash table when the View is removed from an interface; and 3) creating a processing thread, and adopting the processing thread to process the View message. The complexity and the redundancy of Activity are lightened, the function development and expansion of the View can be effectively enhanced, and the control of the View by the Activity is not affected.

Description

technical field [0001] The invention relates to the technical field of communication, in particular to a communication method between Views in an Android system. Background technique [0002] In the Android system, the View component is responsible for the display and processing of the touch screen time, and the click event on the screen is also processed by the View. The Activity as the View container manages the View and is responsible for the layout of the View and life cycle related operations such as creation and removal. When components such as Activity / Service / Broadcast receive relevant driver messages, they will update the display of View. [0003] During the operation of the interface, if the display status of View changes due to user clicks or various system status changes, View needs to notify the manager Activity so that Activity can perform related processing. To this end, the Android system defines a set of callback functions for the View component. After the...

AI Technical Summary

Problems solved by technology

[0005] (1) There is no direct interaction channel between View and View. A single View can only interact with the Activity where it is located, and then the Activity interacts with other Views, so that the entire process needs to be controlled by the Activity, which increases the Activity the complexity of

[0006] (2) Many activities have the same operation on View, and each activity needs to re-implement the corresponding operation, which increases the redundancy of the activity

However, the existing technology does not support the communication mechanism between View and View, and completely maintains the isolation between View and View.

Images