CN109710350B - Cross-screen status bar implementation method based on Android system - Google Patents
Cross-screen status bar implementation method based on Android system Download PDFInfo
- Publication number
- CN109710350B CN109710350B CN201811476568.5A CN201811476568A CN109710350B CN 109710350 B CN109710350 B CN 109710350B CN 201811476568 A CN201811476568 A CN 201811476568A CN 109710350 B CN109710350 B CN 109710350B
- Authority
- CN
- China
- Prior art keywords
- screen
- status bar
- starting point
- auxiliary
- executing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Telephone Function (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention discloses a cross-screen status bar implementation method based on an Android system. Step S1: and continuously monitoring the touch input information to judge whether the status bar of the main screen is awakened, if so, executing the step S2, and otherwise, repeatedly executing the step S1. Step S2: and judging whether the APP running in the secondary screen needs to be displayed in a full screen mode, if so, executing the step S3, and otherwise, executing the step S4. Step S3: the default starting point is modified to create a status bar for the secondary screen. Step S4: creating a status bar for the secondary screen according to a default starting point. According to the method for realizing the cross-screen status bar based on the Android system, the two status bars are simultaneously displayed on the main screen and the auxiliary screen, and the two status bars respectively appearing on the main screen and the auxiliary screen can independently display different status information. In addition, the status bar appearing on the secondary screen does not cover the APP on the secondary screen, so as not to affect the user operation.
Description
Technical Field
The invention belongs to the technical field of vehicle machine application, and particularly relates to a cross-screen status bar implementation method based on an Android system.
Background
At present, various types of vehicles such as fuel vehicles and new energy vehicles are rapidly developed. Meanwhile, similar to the development trend of handheld mobile terminals, the vehicle-mounted system is also obviously changed from a full-keyboard mobile phone represented by a blackberry brand to a full-touch mobile phone represented by an apple brand.
It is worth noting that most of the former vehicle-mounted devices adopt a key input mode or a knob input mode. In the central control area, a plurality of keys and knobs are arranged at the same time. With the development of car machine systems, some car machine systems are gradually configured with touch display screens according to the development trend. The touch display screen gradually evolves to a currently common touch interactive mode through iterative upgrade of a plurality of technologies such as a resistive screen and a capacitive screen.
However, the above touch interactive method still has drawbacks. At present, a common car machine system only has one screen for touch interaction, and therefore, in a common case, the front end can only run one application (APP, the same applies below) at the same time. On this basis, a car machine with two screens for touch interaction has also appeared. Although the two touch interactive screens can display different interfaces and run the two applications independently, only one of the two screens appears in the system status bar. For example, when the main screen has a system status bar, the sub-screen has no system status bar, thereby causing inconvenience to the user.
Disclosure of Invention
Aiming at the situation of the prior art, the invention overcomes the defects and provides a cross-screen status bar implementation method based on an Android system.
The invention adopts the following technical scheme that the method for realizing the cross-screen status bar based on the Android system comprises the following steps:
step S1: continuously monitoring touch input information to judge whether to awaken the status bar of the main screen, if so, executing the step S2, otherwise, repeatedly executing the step S1;
step S2: judging whether the APP running on the secondary screen needs to be displayed in a full screen mode, if so, executing a step S3, otherwise, executing a step S4;
step S3: modifying the default starting point to create a status bar for the secondary screen;
step S4: creating a status bar for the secondary screen according to a default starting point.
According to the above technical solution, step S3 specifically includes the following steps:
step S3.1: acquiring a default starting point of a drawing window area of an APP of a secondary screen;
step S3.2: modifying the default starting point into a correction starting point through PhoneWindowManager to just avoid the state bar of the auxiliary screen from covering the APP of the auxiliary screen;
step S3.3: creating a virtual display form on the auxiliary screen according to the correction starting point;
step S3.4: and creating a status bar of the auxiliary screen through the virtual display form of the auxiliary screen.
According to the above technical solution, step S4 specifically includes the following steps:
step S4.1: acquiring a default starting point of a drawing window area of an APP of a secondary screen;
step S4.2: creating a virtual display form on the secondary screen according to the default starting point;
step S4.3: and creating a status bar of the auxiliary screen through the virtual display form of the auxiliary screen.
According to the technical scheme, the method for implementing the cross-screen status bar based on the Android system further comprises a step S5, wherein the step S5 is located after the step S4:
step S5: and different state information is independently displayed on the state bar of the main screen and the state bar of the auxiliary screen.
The method for realizing the cross-screen status bar based on the Android system has the advantages that two different applications and two different application interfaces are operated on the main screen and the auxiliary screen, the applications of the main screen and the auxiliary screen can be simultaneously and independently operated, and the two status bars can be simultaneously displayed on the main screen and the auxiliary screen. Meanwhile, the two status bars respectively appearing on the main and auxiliary screens can independently display different status information. In addition, the status bar appearing on the secondary screen does not cover (partially cover) the APP of the secondary screen, so as not to affect the user operation.
Drawings
FIG. 1 is a schematic flow diagram of a preferred embodiment of the present invention.
Detailed Description
The invention discloses a cross-screen status bar implementation method based on an Android system, and the specific implementation mode of the invention is further described in combination with the preferred embodiment.
It is worth mentioning that "Statusbar" referred to in the patent application of the present invention is defined as "status column"; the invention relates to the Presentation which is defined as a virtual display form; the invention relates to a PhoneWindowManager which is defined as a window management service; the Android related to the patent application is defined as an open source terminal operating system based on a Linux platform; the invention relates to an APP (application), which is defined as an application running in an Android system.
Preferred embodiments.
Referring to fig. 1 of the drawings, fig. 1 shows a related flow of the cross-screen status bar implementation method based on the Android system.
Preferably, the method for implementing the cross-screen status bar based on the Android system comprises the following steps:
step S1: continuously monitoring the touch input information to judge whether to awaken the status bar of the main screen, if so, executing the step S2, otherwise, repeating the step S1 (continuously monitoring to judge whether to awaken the status bar of the main screen);
step S2: judging whether the APP (application) running on the secondary screen needs to be displayed in a full screen mode, if so, executing the step S3, otherwise, executing the step S4;
step S3: modifying the default starting point to create a status bar for the secondary screen;
step S4: creating a status bar for the secondary screen according to a default starting point.
Further, step S3 specifically includes the following steps:
step S3.1: acquiring a default starting point of a drawing window area of an APP of a secondary screen;
step S3.2: modifying the default starting point into a correction starting point through PhoneWindowManager to just avoid the state bar of the auxiliary screen from covering (partially covering) the APP of the auxiliary screen;
step S3.3: creating a virtual display form on the auxiliary screen according to the correction starting point;
step S3.4: and creating a status bar of the auxiliary screen through the virtual display form of the auxiliary screen.
Further, step S4 specifically includes the following steps:
step S4.1: acquiring a default starting point of a drawing window area of an APP of a secondary screen;
step S4.2: creating a virtual display form on the secondary screen according to the default starting point;
step S4.3: and creating a status bar of the auxiliary screen through the virtual display form of the auxiliary screen.
Further, the method for implementing the cross-screen status bar based on the Android system further includes step S5, where step S5 is located after step S4:
step S5: and different state information is independently displayed on the state bar of the main screen and the state bar of the auxiliary screen.
According to the preferred embodiment, the method for realizing the cross-screen status bar based on the Android system, disclosed by the patent application of the invention, has the advantages that two different applications and two different application interfaces are operated on the main screen and the auxiliary screen, the applications of the main screen and the auxiliary screen can be simultaneously and independently operated, and the two status bars can be simultaneously displayed on the main screen and the auxiliary screen. Meanwhile, the two status bars respectively appearing on the main and auxiliary screens can independently display different status information. In addition, the status bar appearing on the secondary screen does not cover (partially cover) the APP of the secondary screen, so as not to affect the user operation.
It will be apparent to those skilled in the art that modifications and equivalents may be made in the embodiments and/or portions thereof without departing from the spirit and scope of the present invention.
Claims (2)
1. A cross-screen status bar implementation method based on an Android system is characterized by comprising the following steps:
step S1: continuously monitoring touch input information to judge whether to awaken the status bar of the main screen, if so, executing the step S2, otherwise, repeatedly executing the step S1;
step S2: judging whether the APP running on the secondary screen needs to be displayed in a full screen mode, if so, executing a step S3, otherwise, executing a step S4;
step S3: modifying the default starting point to create a status bar for the secondary screen;
step S3 specifically includes the following steps:
step S3.1: acquiring a default starting point of a drawing window area of an APP of a secondary screen;
step S3.2: modifying the default starting point into a correction starting point through PhoneWindowManager to just avoid the state bar of the auxiliary screen from covering the APP of the auxiliary screen;
step S3.3: creating a virtual display form on the auxiliary screen according to the correction starting point;
step S3.4: creating a status bar of the auxiliary screen through the virtual display window of the auxiliary screen;
step S4: creating a status bar of the secondary screen according to a default starting point;
step S4 specifically includes the following steps:
step S4.1: acquiring a default starting point of a drawing window area of an APP of a secondary screen;
step S4.2: creating a virtual display form on the secondary screen according to the default starting point;
step S4.3: and creating a status bar of the auxiliary screen through the virtual display form of the auxiliary screen.
2. The Android system-based screen crossing state bar implementation method of claim 1, wherein the Android system-based screen crossing state bar implementation method further comprises step S5, and step S5 is located after step S4:
step S5: and different state information is independently displayed on the state bar of the main screen and the state bar of the auxiliary screen.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811476568.5A CN109710350B (en) | 2018-12-05 | 2018-12-05 | Cross-screen status bar implementation method based on Android system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811476568.5A CN109710350B (en) | 2018-12-05 | 2018-12-05 | Cross-screen status bar implementation method based on Android system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109710350A CN109710350A (en) | 2019-05-03 |
| CN109710350B true CN109710350B (en) | 2021-12-03 |
Family
ID=66253952
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811476568.5A Active CN109710350B (en) | 2018-12-05 | 2018-12-05 | Cross-screen status bar implementation method based on Android system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109710350B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104936041A (en) * | 2015-06-10 | 2015-09-23 | 福建新大陆通信科技股份有限公司 | Method and system for customizing set top box status bar |
| CN106911859A (en) * | 2017-03-10 | 2017-06-30 | 深圳天珑无线科技有限公司 | Status bar control method and device |
| CN107145317A (en) * | 2011-02-10 | 2017-09-08 | 三星电子株式会社 | Device including multiple touch-screens and the screen changing method for described device |
| CN108205403A (en) * | 2018-01-25 | 2018-06-26 | 中兴通讯股份有限公司 | Displaying method of terminal, device, terminal and computer readable storage medium |
| CN108319416A (en) * | 2018-03-16 | 2018-07-24 | 联想(北京)有限公司 | A kind of display control method, device and electronic equipment |
-
2018
- 2018-12-05 CN CN201811476568.5A patent/CN109710350B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107145317A (en) * | 2011-02-10 | 2017-09-08 | 三星电子株式会社 | Device including multiple touch-screens and the screen changing method for described device |
| CN104936041A (en) * | 2015-06-10 | 2015-09-23 | 福建新大陆通信科技股份有限公司 | Method and system for customizing set top box status bar |
| CN106911859A (en) * | 2017-03-10 | 2017-06-30 | 深圳天珑无线科技有限公司 | Status bar control method and device |
| CN108205403A (en) * | 2018-01-25 | 2018-06-26 | 中兴通讯股份有限公司 | Displaying method of terminal, device, terminal and computer readable storage medium |
| CN108319416A (en) * | 2018-03-16 | 2018-07-24 | 联想(北京)有限公司 | A kind of display control method, device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109710350A (en) | 2019-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105354003A (en) | Display method and device based on interconnection of mobile terminal and car-mounted terminal | |
| CN105653336A (en) | Method for integrating application under double operating systems | |
| CN103955393A (en) | Method and device for starting application program | |
| CN104182196A (en) | Multi-screen display method and mobile terminal | |
| CN103747414A (en) | Method for updating state information and mobile terminals | |
| CN104571928A (en) | Interface display control method and device | |
| WO2022194003A1 (en) | Screen capture method and apparatus, electronic device, and readable storage medium | |
| CN105786340A (en) | Terminal screen display method and apparatus | |
| US20110291942A1 (en) | Display method, application program and computer readable medium for computer key function | |
| CN107734148A (en) | Application display method, device, terminal and computer-readable recording medium | |
| US20120319958A1 (en) | Portable information terminal and key arrangement alteration method therefor | |
| CN104281318A (en) | Method and apparatus to reduce display lag of soft keyboard presses | |
| CN105824562A (en) | Touch control method and touch control system | |
| WO2024099134A1 (en) | Method and apparatus for displaying information on instrument screen, and electronic device and vehicle | |
| CN109710350B (en) | Cross-screen status bar implementation method based on Android system | |
| CN108417214B (en) | Intelligent vehicle-mounted voice assisting method, intelligent voice equipment, terminal and storage medium | |
| JP6171549B2 (en) | Display control apparatus and program | |
| CN103062987A (en) | Refrigerator and control method thereof | |
| JP7015917B2 (en) | Equipment management device using touch panel and management screen generation method | |
| EP2998859B1 (en) | Display control device, display control method, and program | |
| CN105302375A (en) | Method and system for operating intelligent terminal touch screen failure area | |
| CN103631505A (en) | Information processing device and character input display method | |
| JP2014228927A (en) | Electronic equipment | |
| US11366587B2 (en) | Electronic device, electronic device control method, and recording medium | |
| CN116016578B (en) | Intelligent voice guiding method based on equipment state and user behavior |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |