WO2016179752A1 - 一种移动设备用户界面的实现方法及装置 - Google Patents
一种移动设备用户界面的实现方法及装置 Download PDFInfo
- Publication number
- WO2016179752A1 WO2016179752A1 PCT/CN2015/078579 CN2015078579W WO2016179752A1 WO 2016179752 A1 WO2016179752 A1 WO 2016179752A1 CN 2015078579 W CN2015078579 W CN 2015078579W WO 2016179752 A1 WO2016179752 A1 WO 2016179752A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- control
- mobile device
- user interface
- sliding
- area
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2203/00—Indexing scheme relating to G06F3/00 - G06F3/048
- G06F2203/048—Indexing scheme relating to G06F3/048
- G06F2203/04804—Transparency, e.g. transparent or translucent windows
Definitions
- the present invention relates to the field of user interfaces, and in particular, to a method and an apparatus for implementing a user interface of a mobile device.
- WindowManager It is a desktop window manager that can easily manage all open windows on the system desktop; it can hide, transparent or set the window, and can also define rules to control the opening of the window.
- WindowManager Click on this view to open the app. Often this view is visible and displayed on top of other applications, causing visual and operational disruption to the user and affecting the user's experience.
- the technical problem to be solved by the present invention is to provide a mobile device capable of avoiding interference to the user's normal use of the mobile device and enhancing the user experience, in view of the above-mentioned defects that cause the user to interfere with the normal use of the mobile device and affect the user experience.
- User interface implementation method and device are provided.
- the technical solution adopted by the present invention to solve the technical problem thereof is to construct a mobile device user interface implementation method, which includes the following steps:
- step B detecting whether there is a trigger action on the mobile device, if yes, performing step B); otherwise, proceeding with the judgment of this step;
- step B determining whether the trigger action is a click action or a slide action, if the click action is performed, performing step C); if the sliding action, performing step E);
- step C) judging whether the application can be opened by clicking, if yes, opening the application, performing step G); otherwise, performing step D);
- step E determining whether the speed or angle of the sliding motion reaches a preset threshold, if yes, opening the application, performing step G); otherwise, performing step F);
- step G determining whether the corresponding sliding event area of the user interface has a slidable control, if so, sliding the slidable control, performing step G); otherwise, discarding the sliding event, performing step G);
- the transparent trigger area is configured on the screen of the mobile device, and the transparent trigger area is used to detect a triggering action on the mobile device.
- the transparent trigger area also includes pre-processing steps:
- step A02 determining whether the current control is clickable or whether there is a child control, if yes, obtaining the length, width, and position of the current control in the screen, performing step A03); otherwise, the current control is no longer judged ;
- step A04 determining whether the current control is slidable, and if so, marking the current control as being covered by the transparent trigger area and sliding, performing step A05); otherwise, performing step A05);
- the step D) further includes:
- step D2) determining whether there is a clickable control capable of receiving the click event, and if so, using the performAction method of the auxiliary service of Android to pass the click event to the clickable control, performing step G); otherwise, discarding the click Event, perform step G).
- the step F) further includes:
- step F1 in the user interface, determine whether there is a slidable control capable of receiving a sliding event in a coordinate area corresponding to the occurrence of the sliding event, and if so, performing step F2); otherwise, discarding the sliding event, performing step G);
- the transparent trigger area includes an L-type transparent trigger area and an inverse L-type transparent trigger area, and the L-type transparent trigger area is located at a lower left side of the screen, and the inverse The L-shaped transparent trigger area is located on the lower right side of the screen.
- the L-type transparent trigger area is divided into a plurality of small areas, and each of the small areas has an identifier when the user is on the L-type trigger area.
- the mobile device acquires operation data of the user on the L-type trigger area, and uploads the operation data to the cloud server, where the cloud server analyzes the received operation data to generate the L-type trigger area.
- the configuration data the mobile device periodically obtains the configuration data from the cloud server, and dynamically adjusts the width of each small area according to the configuration data; the preset threshold is from the cloud server.
- the configuration data includes a small area identifier, an application package name, an Activity class name, a small area width, a small area sliding speed threshold, and an angle range.
- the present invention also relates to an apparatus for implementing the above-described implementation method of a mobile device user interface, including:
- Trigger detection unit used to detect whether there is a trigger action on the mobile device
- a trigger action determining unit configured to determine whether the trigger action is a click action or a slide action
- Click judgment unit used to determine whether the application can be opened by clicking, if yes, open the application; otherwise, determine whether there is a clickable control at the coordinates of the click event corresponding to the user interface;
- the clickable control judging unit is configured to determine whether there is a clickable control at a coordinate of the click event corresponding to the user interface, and if so, click the clickable control; otherwise, discard the click event;
- the sliding motion determining unit is configured to determine whether the speed or the angle of the sliding motion reaches a preset threshold, and if yes, open the application; otherwise, determine whether the corresponding sliding event region of the user interface has a slidable control;
- a sliding control determining unit configured to determine whether a corresponding sliding event area of the user interface has a slidable control, and if so, sliding the slidable control; otherwise, discarding the sliding event;
- End unit Used to end this operation.
- the screen of the mobile device is provided with a transparent triggering area, the transparent triggering area is used for detecting a triggering action on the mobile device, and the device further includes:
- the control acquiring unit is configured to start acquiring a root node control in the user interface when the user switches the different applications by using the mobile device or switches or slides the interface in the application in different interfaces of the same application;
- the control judging unit is configured to determine whether the current control is clickable or has a child control, and if so, obtain the length, width, and position of the current control; otherwise, the current control is no longer judged;
- a control coverage determining unit configured to determine whether the current control is covered by the transparent trigger area, and if so, marking the current control as being covered by a transparent trigger area and clicking; otherwise, the current control is no longer judged ;
- the control slide determination unit is configured to determine whether the current control is slidable, and if so, mark the current control as being covered by the transparent trigger area and can slide; otherwise, acquiring the next child control;
- Child control get unit used to get the next child control.
- the clickable control determining unit further includes:
- Traversing module traversing a user interface covered by the transparent trigger area according to a coordinate position where a click event occurs;
- a clickable control presence judging module configured to determine whether there is a clickable control capable of receiving the click event, and if so, using a performAction method of an auxiliary service of Android to pass the click event to the clickable control; otherwise, discarding the Click event.
- the sliding control determining unit further includes:
- a slidable control presence judging module configured to determine, in the user interface, whether there is a slidable control capable of receiving a sliding event in a coordinate area corresponding to the occurrence of the sliding event, and if yes, passing the sliding event to the slidable control; otherwise Discarding the sliding event;
- Delivery module for passing the sliding event to the slidable control using a performAction method of an auxiliary service of Android.
- the transparent trigger region includes an L-type transparent trigger region and an inverse L-type transparent trigger region, the L-shaped transparent trigger region is located at a lower left side of the screen, and the inverse L-type transparent trigger region is located The lower right side of the screen.
- the L-type transparent trigger area is divided into a plurality of small areas, and each of the small areas has an identifier.
- the mobile device Obtaining operation data of the user on the L-type trigger area, and uploading the operation data to a cloud server, where the cloud server analyzes the received operation data to generate configuration data of the L-type trigger area,
- the mobile device periodically obtains the configuration data from the cloud server, and dynamically adjusts the width of each small area according to the configuration data; the preset threshold is from the cloud server.
- the configuration data includes a small area identifier, an application package name, an Activity class name, a small area width, a small area sliding speed threshold, and an angle range.
- the implementation method and device for implementing the mobile device user interface of the present invention have the following beneficial effects: when the triggering action fails to reach the condition of opening the application, the user's sliding and click event is transmitted to the user interface covered by the transparent trigger area. In this way, the interference caused by the normal use of the mobile device by the user is avoided, so that it can avoid interference to the normal use of the mobile device by the user and enhance the user experience.
- FIG. 1 is a flowchart of a method for implementing a mobile device user interface in an embodiment of a mobile device user interface according to an embodiment of the present invention
- Figure 2 is a flow chart of the pre-processing steps in the embodiment
- FIG. 3 is a specific flowchart of determining whether there is a clickable control at a coordinate of a click event corresponding to a user interface in the embodiment
- FIG. 4 is a specific flowchart of determining whether a corresponding sliding event area of a user interface has a slidable control in the embodiment
- FIG. 5 is a schematic diagram of dividing an L-type transparent trigger region into a plurality of small regions in the embodiment
- Figure 6 is a schematic view showing the structure of the apparatus in the embodiment.
- FIG. 1 a flowchart of a method for implementing the mobile device user interface is shown in FIG. 1 .
- the implementation method of the mobile device user interface includes the following steps:
- Step S101 detecting whether there is a triggering action on the mobile device: in this step, detecting whether there is a triggering action on the mobile device, specifically detecting whether there is a triggering action on the screen of the mobile device (in this embodiment, the touch screen), if the detection result is If yes, go to step S102; otherwise, continue with the judgment of this step.
- Step S102 determines whether the triggering action is a click action or a slide action: if the result of the above step S101 is YES, the present step is executed. In this step, it is determined whether the trigger action is a click action or a slide action, and if it is a click action, step S103 is performed; if it is a slide motion, step S108 is performed.
- Step S103 determines whether the application can be opened by clicking: if the result of the determination in the above step S102 is a click action, the present step is executed. In this step, it is judged whether the application can be opened by clicking, and if the result of the determination is YES, step S104 is performed; otherwise, step S105 is performed.
- Step S105 It is determined whether there is a clickable control at the coordinates of the click event corresponding to the user interface: if the result of the above step S103 is no, the step is executed. In this step, it is determined whether there is a clickable control at the coordinates of the click event corresponding to the user interface. If the result of the determination is yes, step S106 is performed; otherwise, step S107 is performed.
- Step S106 Clicking the clickable control: If the result of the above step S105 is YES, the step is executed. In this step, click on the above clickable controls. After performing this step, step S112 is performed.
- Step S107 Discarding the click event: If the result of the above step S105 is NO, the step is executed. In this step, the click event is discarded. After performing this step, step S112 is performed.
- Step S108 It is determined whether the speed or angle of the sliding motion reaches a preset threshold: if the result of the above step S102 is a sliding motion, the present step is performed. In this step, it is determined whether the speed or angle of the sliding motion reaches a preset threshold, and the preset threshold is a threshold that can open the application. In this step, if the result of the determination is yes, then step S104 is performed; otherwise, step S109 is performed.
- Step S109 determining whether the corresponding sliding event area of the user interface has a slidable control: if the result of the above step S108 is no, the step is performed. In this step, it is determined whether there is a slidable control in the corresponding sliding event area of the user interface. If the result of the determination is yes, step S110 is performed; otherwise, step S111 is performed.
- Step S110 Slide slidable control: If the result of the above step S109 is YES, the step is executed. In this step, slide the slidable control. After performing this step, step S112 is performed.
- Step S111 Discarding the slip event: If the result of the above step S109 is NO, the step is executed. In this step, the sliding event is discarded. After performing this step, step S112 is performed.
- Step S112 ends the current operation: in this step, the current operation is ended.
- a global portal for easily opening an application is implemented on the mobile device. Since the sliding event and the click event of the user are transmitted to the user interface covered by the transparent trigger area when the triggering action fails to reach the condition of opening the application, the interference caused by the normal use of the mobile device by the user is avoided, so Avoid interference with users' normal use of mobile devices and enhance user experience.
- a transparent trigger area is configured on the screen of the mobile device, and the transparent trigger area is used to detect a triggering action on the mobile device.
- the transparent trigger area includes an L-type transparent trigger area and an inverse L-type transparent trigger area, and the L-type transparent
- the trigger area is located on the lower left side of the screen, specifically, an L-shaped ( ⁇ ) transparent trigger area is presented on the lower left side of the screen, and the inverse L-type transparent trigger area is located on the lower right side of the screen, specifically showing an inverse on the lower right side of the screen.
- L-shaped ( ⁇ ) transparent trigger area is further included before the step S101 above, and a specific flowchart of the pre-processing step is shown in FIG. 2. In Figure 2, the above pre-processing steps include:
- Step S01 When the user switches the different applications by using the mobile device or switches in different interfaces of the same application or slides the interface in the application, the root node control in the user interface is started: in this step, when the user uses the mobile device to switch different When the application switches or slides the interface in the application in different interfaces of the same application, the root node control in the user interface is started, specifically, when the user uses the mobile device to switch different applications, or in different interfaces of the same application.
- the AccessibilityService's onAccessibilityEvent method is triggered when you switch or slide the interface in your app. In the onAccessibilityEvent method, find the root node control in the user interface, and then perform subsequent operations.
- Step S02 determines whether the current control is clickable or has a child control: in this step, it is determined whether the current control is clickable or whether there is a child control. If the result of the determination is yes, step S04 is performed; otherwise, step S03 is performed.
- step S03 the current control is no longer judged: if the result of the above step S02 is no, the step is executed. In this step, the current control is no longer judged.
- Step S04 Obtain the length, width, and position of the current control: If the result of the above step S02 is YES, perform this step. In this step, you get the length, width, and position of the current control. After performing this step, step S05 is performed.
- Step S05 Determining whether the current control is covered by the transparent trigger area: in this step, determining whether the current control is covered by the transparent trigger area, that is, determining whether the current control intersects with the transparent trigger area, and if the result of the determination is yes, executing step S06; otherwise, Go back to step S03.
- Step S06 The current control is marked as covered by the transparent trigger area and can be clicked: if the result of the above step S05 is YES, then this step is performed. In this step, the current control is marked as covered by the transparent trigger area and can be clicked.
- Step S07 determines whether the current control is slidable: in this step, it is determined whether the current control is slidable. If the result of the determination is yes, step S08 is performed; otherwise, step S09 is performed.
- Step S08 At the same time, the current control is marked as covered by the transparent trigger area and can be slid: if the result of the above step S07 is YES, that is, the current control can also slide at the same time, this step is performed. In this step, the current control is marked as being covered by the transparent trigger area and can be slid. After performing this step, go to step S09.
- Step S09 Get the next child control: In this step, the next child control is obtained, and the step is executed, and the process returns to step S02. That is, for each sub-control of the secondary control, the above judgment and marking are repeated. In this way, when a sliding event or a click event on the transparent trigger area needs to be passed to the user interface under the transparent trigger area, the controls that need to receive the event can be found from the marked controls according to the coordinates of the event. Through the pre-processing step, it is possible to find a control that is received by the transparent trigger area and receives the event in the user interface corresponding to the position of the sliding event or the click event in the transparent area. Its operation is quick and convenient.
- the above steps S105 to S107 can be further refined, and the refined flowchart is as shown in FIG. 3.
- the above steps S105 to S107 further include:
- Step S51 According to the coordinate position where the click event occurs, the user interface covered by the transparent trigger area is traversed: in this step, in this step, the user interface covered by the transparent trigger area is traversed according to the coordinate position where the click event occurs.
- Step S52 determining whether there is a clickable control capable of receiving the click event: in this step, determining whether there is a clickable control capable of receiving the click event, if the result of the determination is yes, executing step S54; otherwise, executing step S53.
- Step S53 discards the click event: if the result of the above step S52 is no, the present step is executed. In this step, the click event is discarded. After performing this step, step S112 is performed.
- Step S54 passes the click event to the clickable control using the performAction method of the auxiliary service of Android: if the result of the above step S52 is YES, the step is executed. In this step, the click event is passed to the clickable control using the performAction method of the Android auxiliary service. This will avoid interference with the normal use of mobile devices by users.
- the above-mentioned steps S109 to S111 can be further refined, and the refined flowchart is as shown in FIG. 4 .
- the above steps S109 to S111 further include:
- Step S91 In the user interface, determining whether there is a slidable control capable of receiving a sliding event in a coordinate area corresponding to the occurrence of the sliding event: in this step, in the user interface, determining whether in the coordinate area corresponding to the occurrence of the sliding event There is a slidable control capable of receiving a sliding event, and if the result of the determination is YES, step S93 is performed; otherwise, step S92 is performed.
- Step S92 Discarding the slip event: If the result of the above step S91 is NO, the step is executed. In this step, the sliding event is discarded. After performing this step, step S112 is performed.
- Step S93 The sliding event is passed to the slidable control using the performAction method of the auxiliary service of Android: if the result of the above step S91 is YES, the step is executed. In this step, the sliding event is passed to the slidable control using the performAction method of the Android auxiliary service. This will avoid interference with the normal use of mobile devices by users.
- the L-type transparent triggering area is divided into a plurality of small areas, and the division diagram is as shown in FIG. 5.
- Each small area has an identifier.
- the mobile device acquires the operation data of the user on the L-type trigger area, and uploads the operation data to the cloud server, and the cloud server performs the operation on the receiving.
- the data is analyzed to form an optimized L-type trigger area size and location configuration, and the configuration data of the L-type trigger area is generated.
- the mobile device periodically obtains the configuration data from the cloud server, and dynamically adjusts the width of each small area according to the configuration data. .
- the above configuration data includes a small area identifier, an application package name, an Activity class name, a small area width, a sliding speed threshold in a small area, and an angle range.
- the L-type trigger area is divided into a plurality of smaller small areas, each of which has a number assigned as an identifier of the small area.
- the application interface When the user slides in the L-type trigger area and reaches the trigger condition (that is, the speed and angle of the user's sliding motion reaches the preset threshold), when the application interface is opened, the identifier of the small area where the sliding starting point position is located is recorded, and the sliding distance/ The angle, the angle between the position when the trigger condition is reached and the angle at which the sliding start point is formed, and the package name and class name of the application activity covered by the L-shaped trigger area.
- the trigger is a misoperation, and the information recorded above is attached to the cloud server.
- a threshold value for the erroneous operation ratio of each small area is set. If the threshold of a certain misoperation ratio is reached, the width of the corresponding small area is set accordingly, and the speed and angle to be reached when the small area slides are limited to reach the trigger condition. Therefore, after obtaining a certain amount of operation data of the user on the L-type trigger area on the cloud server, it can be counted that when the L-type trigger area is overlaid on each Activity of each application, each small area is The proportion of false actions that are triggered. According to the threshold of the false operation of the trigger and the threshold of the misoperation of the corresponding small area, a configuration of the L-type trigger area can be generated for each Activity of each application. Each entry in this configuration includes: small area ID, application package name, Activity class name, small area width, sliding speed threshold and angle range in the small area. It is worth mentioning that the preset threshold in the above step S108 is from the cloud server.
- the application of the mobile device periodically obtains the configuration data of the L-type trigger area from the cloud server, and then dynamically adjusts the width of each small area according to the configuration data and the application run by the current user, and when the user slides in the small area, only The sliding speed reaches the speed threshold of the small area, and the trigger condition can be satisfied when the angle is within a given range.
- the user continues to upload the operation data of the user on the L-type trigger area, forming an operation data upload, cloud server analysis, generating configuration data, obtaining configuration data adjustment trigger area, and then continuing to operate data upload, cloud server analysis, etc.
- a complete loop that continuously optimizes the L-shaped trigger area to enhance the user experience.
- the embodiment further relates to an apparatus for implementing the foregoing user interface of a mobile device, and a schematic structural diagram thereof is shown in FIG. 6.
- the device includes a trigger detecting unit 1, a trigger action determining unit 2, a click determining unit 3, a clickable control determining unit 4, a sliding motion determining unit 5, a sliding control determining unit 6, and an ending unit 7; wherein, the trigger detecting The unit 1 is configured to detect whether there is a triggering action on the mobile device; the triggering action determining unit 2 is configured to determine whether the triggering action is a clicking action or a sliding action; the click determining unit 3 is configured to determine whether the application can be opened by clicking, and if so, opening the application; otherwise Determining whether there is a clickable control at the coordinates of the click event corresponding to the user interface; the clickable control determining unit 4 is configured to determine whether there is a clickable control at the coordinates of the click event corresponding to the user interface, if yes, click to click the control; otherwise, discard the trigger
- a transparent trigger area is disposed on the screen of the mobile device, and the transparent trigger area is used to detect a trigger action on the mobile device.
- the transparent trigger area includes an L-type transparent trigger area and an inverse L-type transparent trigger area, and the L-type transparent trigger is triggered.
- the area is located on the lower left side of the screen, and the inverted L-shaped transparent trigger area is located on the lower right side of the screen.
- the device further includes a control acquiring unit 01, a control determining unit 02, a control covering determining unit 03, a control sliding determining unit 04, and a child control acquiring unit 05; wherein the control acquiring unit 01 is configured to switch different applications or use the mobile device when the user When the different interfaces of the same application switch or slide the interface in the application, the root node control in the user interface is started; the control determining unit 02 is configured to determine whether the current control is clickable or whether there is a child control, and if so, obtain the current control.
- control overlay determination unit 03 is used to determine whether the current control is covered by the transparent trigger area, and if so, the current control is marked as covered by the transparent trigger area and Clickable; otherwise, the current control is no longer judged;
- control slide determination unit 04 is used to determine whether the current control is slidable, and if so, the current control is marked as being covered by the transparent trigger area and can be slid; otherwise, the next child is obtained.
- Control; child control acquisition unit 05 is used to obtain the next Child controls.
- the clickable control determining unit 4 further includes a traversing module 41 and a clickable control presence determining module 42.
- the traversing module 41 is configured to traverse the user interface covered by the transparent triggering area according to the coordinate position where the click event occurs;
- the clickable control presence determining module 42 is configured to determine whether there is a clickable control capable of receiving a click event, and if so, use the performAction method of the Android auxiliary service to pass the click event to the clickable control; otherwise, the click event is discarded.
- the sliding control determining unit 6 further includes a slidable control presence determining module 61 and a transmitting module 62.
- the slidable control presence determining module 61 is configured to determine, in the user interface, a coordinate region corresponding to the occurrence of the sliding event. Whether there is a slidable control capable of receiving a sliding event, for example, passing a sliding event to the slidable control; otherwise, discarding the sliding event; the delivery module 62 is configured to pass the sliding event to the slidable control using the performAction method of the Android auxiliary service .
- the user's sliding event or click event is transmitted to the user interface covered by the L-shaped transparent triggering area or the inverse L-shaped transparent triggering area. In this way, it can avoid interference to the normal use of the mobile device by the user, and greatly enhance the user experience.
Abstract
本发明提出了一种移动设备用户界面的实现方法及装置，方法包括：检测是否有触发动作，如是，执行下一步骤；否则，继续本步骤的判断；判断是点击动作还是滑动动作，如是点击动作，执行下一步骤；如是滑动动作，进行滑动动作的判断；判断是否可以打开应用，如是，打开应用；否则，执行下一步骤；判断是否有可点击控件，如是，点击可点击控件；否则，丢弃点击事件；判断滑动动作的速度或角度是否达到预设阈值，如是，打开应用；否则，执行下一步骤；判断是否有可滑动控件，如是，滑动可滑动控件；否则，丢弃滑动事件；结束。实施本发明的移动设备用户界面的实现方法及装置，具有以下有益效果：能避免对用户正常使用移动设备造成干扰、增强用户体验。
Description
本发明涉及用户界面领域，特别涉及一种移动设备用户界面的实现方法及装置。
WindowManager
是一个桌面窗口管理器，可以方便地管理系统桌面上的所有打开的窗口；可以隐藏、透明化或者置顶窗口，还可以制定相应的规则来控制窗口的打开。为了在 Android
移动设备中实现一个全局的应用入口，很多应用都会使用 WindowManager 添加一个视图（ View
），点击这个视图可以打开应用。通常这个视图都是可见的，显示于其他应用之上，因而会对用户造成视觉和操作上的干扰，影响用户的体验。
本发明要解决的技术问题在于，针对现有技术的上述对用户正常使用移动设备造成干扰、影响用户体验的缺陷，提供一种能避免对用户正常使用移动设备造成干扰、增强用户体验的移动设备用户界面的实现方法及装置。
本发明解决其技术问题所采用的技术方案是：构造一种移动设备用户界面的实现方法，包括如下步骤：
A）检测移动设备上是否有触发动作，如是，执行步骤B）；否则，继续进行本步骤的判断；
B）判断所述触发动作是点击动作还是滑动动作，如是点击动作，则执行步骤C）；如是滑动动作，则执行步骤E）；
C）判断是否可以通过点击打开应用，如是，打开应用，执行步骤G）；否则，执行步骤D）；
D）判断用户界面对应点击事件的坐标处是否有可点击控件，如是，点击所述可点击控件，执行步骤G）；否则，丢弃所述点击事件，执行步骤G）；
E）判断所述滑动动作的速度或角度是否达到预设阈值，如是，打开应用，执行步骤G）；否则，执行步骤F）；
F）判断用户界面相应滑动事件区域是否有可滑动控件，如是，滑动所述可滑动控件，执行步骤G）；否则，丢弃所述滑动事件，执行步骤G）；
G）结束本次操作。
在本发明所述的移动设备用户界面的实现方法中，所述移动设备的屏幕上设有透明触发区域，所述透明触发区域用以检测对所述移动设备的触发动作，在所述步骤A）之前还包括预处理步骤：
A01）当用户使用移动设备切换不同的应用或者在同一应用的不同界面进行切换或滑动应用中的界面时，开始获取用户界面中的根节点控件；
A02）判断当前控件是否可点击或是否有子控件，如是，获取所述当前控件的长度、宽度以及在所述屏幕中的位置，执行步骤A03）；否则，不再对所述当前控件进行判断；
A03）判断所述当前控件是否被所述透明触发区域覆盖，如是，将所述当前控件标记为被透明触发区域覆盖并可点击，执行步骤A04）；否则，不再对所述当前控件进行判断；
A04）判断所述当前控件是否可滑动，如是，同时将所述当前控件标记为被透明触发区域覆盖并可滑动，执行步骤A05）；否则，执行步骤A05）；
A05）获取下一个子控件，并返回步骤A02）。
在本发明所述的移动设备用户界面的实现方法中，所述步骤D）进一步包括：
D1）根据点击事件发生的坐标位置，遍历所述透明触发区域所覆盖的用户界面；
D2）判断是否存在能接收所述点击事件的可点击控件，如是，使用Android的辅助服务的performAction方法将所述点击事件传递给所述可点击控件，执行步骤G）；否则，丢弃所述点击事件，执行步骤G）。
在本发明所述的移动设备用户界面的实现方法中，所述步骤F）进一步包括：
F1）在用户界面中，判断在对应于滑动事件发生的坐标区域内是否存在能接收滑动事件的可滑动控件，如是，执行步骤F2）；否则，丢弃所述滑动事件，执行步骤G)；
F2）使用Android的辅助服务的performAction方法将所述滑动事件传递给所述可滑动控件，执行步骤G）。
在本发明所述的移动设备用户界面的实现方法中，所述透明触发区域包括L型透明触发区域和反L型透明触发区域，所述L型透明触发区域位于屏幕的左下侧，所述反L型透明触发区域位于所述屏幕的右下侧。
在本发明所述的移动设备用户界面的实现方法中，所述L型透明触发区域划分为多个小区域，每个所述小区域均有一个标识，当用户在所述L型触发区域上进行操作时，移动设备获取用户在所述L型触发区域上的操作数据，并将所述操作数据上传到云端服务器，所述云端服务器对接收的操作数据进行分析，生成所述L型触发区域的配置数据，所述移动设备定期从所述云端服务器获取所述配置数据，并依据所述配置数据动态调整所述每个小区域的宽度；所述预设阈值来自所述云端服务器。
在本发明所述的移动设备用户界面的实现方法中，所述配置数据包括小区域标识、应用包名、Activity类名、小区域宽度、小区域内滑动速度阈值和角度范围。
本发明还涉及一种实现上述移动设备用户界面的实现方法的装置，包括：
触发检测单元：用于检测移动设备上是否有触发动作；
触发动作判断单元：用于判断所述触发动作是点击动作还是滑动动作；
点击判断单元：用于判断是否可以通过点击打开应用，如是，打开应用；否则，判断用户界面对应点击事件的坐标处是否有可点击控件；
可点击控件判断单元：用于判断用户界面对应点击事件的坐标处是否有可点击控件，如是，点击所述可点击控件；否则，丢弃所述点击事件；
滑动动作判断单元：用于判断所述滑动动作的速度或角度是否达到预设阈值，如是，打开应用；否则，判断用户界面相应滑动事件区域是否有可滑动控件；
滑动控件判断单元：用于判断用户界面相应滑动事件区域是否有可滑动控件，如是，滑动所述可滑动控件；否则，丢弃所述滑动事件；
结束单元：用于结束本次操作。
在本发明所述的装置中，所述移动设备的屏幕上设有透明触发区域，所述透明触发区域用以检测对所述移动设备的触发动作，所述装置还包括：
控件获取单元：用于当用户使用移动设备切换不同的应用或者在同一应用的不同界面进行切换或滑动应用中的界面时，开始获取用户界面中的根节点控件；
控件判断单元：用于判断当前控件是否可点击或是否有子控件，如是，获取所述当前控件的长度、宽度以及在所述屏幕中的位置；否则，不再对所述当前控件进行判断；
控件覆盖判断单元：用于判断所述当前控件是否被所述透明触发区域覆盖，如是，将所述当前控件标记为被透明触发区域覆盖并可点击；否则，不再对所述当前控件进行判断；
控件滑动判断单元：用于判断所述当前控件是否可滑动，如是，同时将所述当前控件标记为被透明触发区域覆盖并可滑动；否则，获取下一个子控件；
子控件获取单元：用于获取下一个子控件。
在本发明所述的装置中，所述可点击控件判断单元进一步包括：
遍历模块：用于根据点击事件发生的坐标位置，遍历所述透明触发区域所覆盖的用户界面；
可点击控件存在判断模块：用于判断是否存在能接收所述点击事件的可点击控件，如是，使用Android的辅助服务的performAction方法将所述点击事件传递给所述可点击控件；否则，丢弃所述点击事件。
在本发明所述的装置中，所述滑动控件判断单元进一步包括：
可滑动控件存在判断模块：用于在用户界面中，判断在对应于滑动事件发生的坐标区域内是否存在能接收滑动事件的可滑动控件，如是，将滑动事件传递给所述可滑动控件；否则，丢弃所述滑动事件；
传递模块：用于使用Android的辅助服务的performAction方法将所述滑动事件传递给所述可滑动控件。
在本发明所述的装置中，所述透明触发区域包括L型透明触发区域和反L型透明触发区域，所述L型透明触发区域位于屏幕的左下侧，所述反L型透明触发区域位于所述屏幕的右下侧。
在本发明所述的装置中，所述L型透明触发区域划分为多个小区域，每个所述小区域均有一个标识，当用户在所述L型触发区域上进行操作时，移动设备获取用户在所述L型触发区域上的操作数据，并将所述操作数据上传到云端服务器，所述云端服务器对接收的操作数据进行分析，生成所述L型触发区域的配置数据，所述移动设备定期从所述云端服务器获取所述配置数据，并依据所述配置数据动态调整所述每个小区域的宽度；所述预设阈值来自所述云端服务器。
在本发明所述的装置中，所述配置数据包括小区域标识、应用包名、Activity类名、小区域宽度、小区域内滑动速度阈值和角度范围。
实施本发明的移动设备用户界面的实现方法及装置，具有以下有益效果：由于在触发动作未能达到打开应用的条件时，将用户的滑动、点击事件下传到透明触发区域所覆盖的用户界面中，这样就避免了对用户正常使用移动设备造成的干扰，所以其能避免对用户正常使用移动设备造成干扰、增强用户体验。
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本发明移动设备用户界面的实现方法及装置一个实施例中移动设备用户界面的实现方法的流程图；
图2为所述实施例中预处理步骤的流程图；
图3为所述实施例中判断用户界面对应点击事件的坐标处是否有可点击控件的具体流程图；
图4为所述实施例中判断用户界面相应滑动事件区域是否有可滑动控件的具体流程图；
图5为所述实施例中L型透明触发区域划分成多个小区域的示意图；
图6为所述实施例中装置的结构示意图。
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
在本发明移动设备用户界面的实现方法及装置实施例中，其移动设备用户界面的实现方法的流程图如图1所示。图1中，该移动设备用户界面的实现方法包括如下步骤：
步骤S101检测移动设备上是否有触发动作：本步骤中，检测移动设备上是否有触发动作，具体就是检测移动设备的屏幕（本实施例中为触摸屏）上是否有触发动作，如果检测的结果为是，则执行步骤S102；否则，继续进行本步骤的判断。
步骤S102判断触发动作是点击动作还是滑动动作：如果上述步骤S101的判断结果为是，则执行本步骤。本步骤中，判断上述触发动作是点击动作还是滑动动作，如果是点击动作，则执行步骤S103；如果是滑动动作，则执行步骤S108。
步骤S103判断是否可以通过点击打开应用：如果上述步骤S102的判断结果为点击动作，则执行本步骤。本步骤中，判断是否可以通过点击打开应用，如果判断的结果为是，则执行步骤S104；否则，执行步骤S105。
步骤S104
打开应用：如果上述步骤S103的判断结果为是，则执行本步骤。本步骤中，打开应用。执行完本步骤，执行步骤S112。
步骤S105
判断用户界面对应点击事件的坐标处是否有可点击控件：如果上述步骤S103的判断结果为否，则执行本步骤。本步骤中，判断用户界面对应点击事件的坐标处是否有可点击控件，如果判断的结果为是，则执行步骤S106；否则，执行步骤S107。
步骤S106
点击可点击控件：如果上述步骤S105的判断结果为是，则执行本步骤。本步骤中，点击上述可点击控件。执行完本步骤，执行步骤S112。
步骤S107
丢弃点击事件：如果上述步骤S105的判断结果为否，则执行本步骤。本步骤中，丢弃点击事件。执行完本步骤，执行步骤S112。
步骤S108
判断滑动动作的速度或角度是否达到预设阈值：如果上述步骤S102的判断结果为滑动动作，则执行本步骤。本步骤中，判断滑动动作的速度或角度是否达到预设阈值，这个预设阈值为可以打开应用的阈值。本步骤中，如果判断的结果为是，则执行步骤S104；否则，执行步骤S109。
步骤S109判断用户界面相应滑动事件区域是否有可滑动控件：如果上述步骤S108的判断结果为否，则执行本步骤。本步骤中，判断用户界面相应滑动事件区域是否有可滑动控件，如果判断的结果为是，则执行步骤S110；否则，执行步骤S111。
步骤S110
滑动可滑动控件：如果上述步骤S109的判断结果为是，则执行本步骤。本步骤中，滑动可滑动控件。执行完本步骤，执行步骤S112。
步骤S111
丢弃滑动事件：如果上述步骤S109的判断结果为否，则执行本步骤。本步骤中，丢弃滑动事件。执行完本步骤，执行步骤S112。
步骤S112结束本次操作：本步骤中，结束本次操作。这样，就在移动设备上实现了便捷地打开应用的全局入口。由于在触发动作未能达到打开应用的条件时，将用户的滑动、点击事件下传到透明触发区域所覆盖的用户界面中，这样就避免了对用户正常使用移动设备造成的干扰，所以其能避免对用户正常使用移动设备造成干扰、增强用户体验。
本实施例中，移动设备的屏幕上设有透明触发区域，该透明触发区域用以检测对移动设备的触发动作，透明触发区域包括L型透明触发区域和反L型透明触发区域，L型透明触发区域位于屏幕的左下侧，具体就是在屏幕的左下侧呈现一个L型（╚）的透明触发区域，反L型透明触发区域位于屏幕的右下侧，具体就是在屏幕右下侧呈现一个反L型（╝）的透明触发区域。在上述步骤S101之前还包括预处理步骤，预处理步骤的具体流程图如图2所示。图2中，上述预处理步骤包括：
步骤S01当用户使用移动设备切换不同的应用或者在同一应用的不同界面进行切换或者滑动应用中的界面时，开始获取用户界面中的根节点控件：本步骤中，当用户使用移动设备切换不同的应用或者在同一应用的不同界面进行切换或滑动应用中的界面时，开始获取用户界面中的根节点控件，具体来讲，当用户使用移动设备切换不同的应用，或者在同一应用的不同界面进行切换，或者滑动应用中的界面时，会触发AccessibilityService的onAccessibilityEvent方法。在onAccessibilityEvent方法中，找到用户界面中的根节点控件，然后进行后续的操作。
步骤S02判断当前控件是否可点击或是否有子控件：本步骤中，判断当前控件是否可点击或是否有子控件，如果判断的结果为是，则执行步骤S04；否则，执行步骤S03。
步骤S03不再对当前控件进行判断：如果上述步骤S02的判断结果为否，则执行本步骤。本步骤中，不再对当前控件进行判断。
步骤S04
获取当前控件的长度、宽度以及在屏幕中的位置：如果上述步骤S02的判断结果为是，则执行本步骤。本步骤中，获取当前控件的长度、宽度以及在屏幕中的位置。执行完本步骤，执行步骤S05。
步骤S05
判断当前控件是否被透明触发区域覆盖：本步骤中，判断当前控件是否被透明触发区域覆盖，也就是判断当前控件是否与透明触发区域相交，如果判断的结果为是，则执行步骤S06；否则，返回步骤S03。
步骤S06
将当前控件标记为被透明触发区域覆盖并可点击：如果上述步骤S05的判断结果为是，则执行本步骤。本步骤中，将当前控件标记为被透明触发区域覆盖并可点击。
步骤S07判断当前控件是否可滑动：本步骤中，判断当前控件是否可滑动，如果判断的结果为是，则执行步骤S08；否则，执行步骤S09。
步骤S08
同时将当前控件标记为被透明触发区域覆盖并可滑动：如果上述步骤S07的判断的结果为是，即当前控件同时也可滑动，则执行本步骤。本步骤中，同时将当前控件标记为被透明触发区域覆盖并可滑动。执行完本步骤，执行步骤S09。
步骤S09
获取下一个子控件：本步骤中，获取下一个子控件，执行完本步骤，返回步骤S02。也就是对于次控件的每个子控件，重复进行上述的判断和标记。这样，当透明触发区域上的滑动事件或点击事件需要传递到透明触发区域下面的用户界面时，即可从已标记的这些控件中根据事件的坐标找出需要接收事件的控件。通过预处理步骤，可以查找透明触发区域所覆盖的，与透明区域中滑动事件或点击事件发生位置相对应的用户界面中的接收事件的控件。其操作快捷方便。
对于本实施例而言，上述步骤S105至步骤S107还可进一步细化，其细化后的流程图如图3所示。图3中，上述步骤S105至步骤S107进一步包括：
步骤S51
根据点击事件发生的坐标位置，遍历透明触发区域所覆盖的用户界面：本步骤中，本步骤中，根据点击事件发生的坐标位置，遍历透明触发区域所覆盖的用户界面。
步骤S52判断是否存在能接收点击事件的可点击控件：本步骤中，判断是否存在能接收点击事件的可点击控件，如果判断的结果为是，则执行步骤S54；否则，执行步骤S53。
步骤S53丢弃点击事件：如果上述步骤S52的判断结果为否，则执行本步骤。本步骤中，丢弃点击事件。执行完本步骤，执行步骤S112。
步骤S54使用Android的辅助服务的performAction方法将点击事件传递给可点击控件：如果上述步骤S52的判断结果为是，则执行本步骤。本步骤中，使用Android的辅助服务的performAction方法将点击事件传递给可点击控件。这样就可避免对用户正常使用移动设备造成干扰。
对于本实施例而言，上述所述步骤S109至步骤S111还可进一步细化，其细化后的流程图如图4所示。图4中，上述步骤S109至步骤S111进一步包括：
步骤S91在用户界面中，判断在对应于滑动事件发生的坐标区域内是否存在能接收滑动事件的可滑动控件：本步骤中，在用户界面中，判断在对应于滑动事件发生的坐标区域内是否存在能接收滑动事件的可滑动控件，如果判断的结果为是，则执行步骤S93；否则，执行步骤S92。
步骤S92
丢弃滑动事件：如果上述步骤S91的判断结果为否，则执行本步骤。本步骤中，丢弃滑动事件。执行完本步骤，执行步骤S112。
步骤S93
使用Android的辅助服务的performAction方法将滑动事件传递给可滑动控件：如果上述步骤S91的判断结果为是，则执行本步骤。本步骤中，使用Android的辅助服务的performAction方法将滑动事件传递给可滑动控件。这样就可避免对用户正常使用移动设备造成干扰。
为了进一步减少L型触发区域对用户操作的干扰，本实施例中，将L型透明触发区域划分为多个小区域，其划分示意图如图5所示。每个小区域均有一个标识，当用户在L型触发区域上进行操作时，移动设备获取用户在L型触发区域上的操作数据，并将操作数据上传到云端服务器，云端服务器对接收的操作数据进行分析，形成优化的L型触发区域大小和位置的配置，生成L型触发区域的配置数据，移动设备定期从云端服务器获取该配置数据，并依据该配置数据动态调整每个小区域的宽度。上述配置数据包括小区域标识、应用包名、Activity类名、小区域宽度、小区域内滑动速度阈值和角度范围。
具体的，本实施例中，当用户在L型触发区域上滑动，然后触发应用界面后的设定时间之内，如果没有任何操作应用界面的行为，而是直接关闭了应用界面时，则将此行为认为是在L型触发区域上的误操作。另外，将L型触发区域划分为多个更小的小区域，每一个小区域有分配一个数字作为该小区域的标识。当用户在L型触发区域滑动并达到触发条件（也就是用户滑动动作的速度和角度达到了预设阈值），打开应用界面时，记录下滑动起始点位置所在的小区域的标识，滑动距离/角度、达到触发条件时的位置与滑动起始点形成的夹角的角度，以及L型触发区域所覆盖的应用Activity的包名和类名等信息。当用户关闭应用界面时，判断此次的触发是否为误操作，并附带上述所记录的信息，上传到云端服务器。
本实施例中，针对每个小区域，设定了每个小区域的关于误操作占比的阈值。如果达到了某一个误操作占比的阈值，就会相应地设定相应的小区域的宽度，并限定在该小区域滑动时需达到多大速度和角度才可达到触发条件。所以，当云端服务器上获取到一定量的用户在L型触发区域上的操作数据之后，可以统计出，当L型触发区域覆盖在每一个应用的每一个Activity之上时，每一个小区域的触发误操作的比例。根据这个触发误操作的比例与相应小区域设定的误操作占比的阈值，就可以针对每一个应用的每一个Activity，生成一份L型触发区域的配置。这份配置的每一个条目中包括：小区域标识、应用包名、Activity类名、小区域宽度、小区域内滑动速度阈值和角度范围。值得一提的是，上述步骤S108中的预设阈值来自云端服务器。
移动设备的应用定期从云端服务器上获取L型触发区域的配置数据，然后根据此配置数据以及当前用户运行的应用，动态调整每一个小区域的宽度，并且，当用户在小区域内滑动时，只有滑动速度达到了该小区域的速度阈值，并且角度在给定的范围时才能满足触发条件。同时，仍然继续上传用户在L型触发区域上的操作数据，形成一个操作数据上传、云端服务器分析、生成配置数据、获取配置数据调整触发区域，然后继续操作数据上传、云端服务器分析……，这样一个完整的循环，持续地优化L型触发区域，提升用户体验。
本实施例还涉及一种上述移动设备用户界面的实现方法的装置，其结构示意图如图6所示。图6中，该装置包括触发检测单元1、触发动作判断单元2、点击判断单元3、可点击控件判断单元4、滑动动作判断单元5、滑动控件判断单元6和结束单元7；其中，触发检测单元1用于检测移动设备上是否有触发动作；触发动作判断单元2用于判断触发动作是点击动作还是滑动动作；点击判断单元3用于判断是否可以通过点击打开应用，如是，打开应用；否则，判断用户界面对应点击事件的坐标处是否有可点击控件；可点击控件判断单元4用于判断用户界面对应点击事件的坐标处是否有可点击控件，如是，点击可点击控件；否则，丢弃点击事件；滑动动作判断单元5用于判断滑动动作的速度或角度是否达到预设阈值，如是，打开应用；否则，判断用户界面相应滑动事件区域是否有可滑动控件；滑动控件判断单元6用于判断用户界面相应滑动事件区域是否有可滑动控件，如是，滑动可滑动控件；否则，丢弃滑动事件；结束单元7用于结束本次操作。这样，就在移动设备上实现了便捷地打开应用的全局入口。由于在触发动作未能达到打开应用的条件时，将用户的滑动、点击事件下传到透明触发区域所覆盖的用户界面中，这样就避免了对用户正常使用移动设备造成的干扰，所以其能避免对用户正常使用移动设备造成干扰、增强用户体验。
本实施例中，移动设备的屏幕上设有透明触发区域，透明触发区域用以检测对移动设备的触发动作，透明触发区域包括L型透明触发区域和反L型透明触发区域，L型透明触发区域位于屏幕的左下侧，反L型透明触发区域位于屏幕的右下侧。该装置还包括控件获取单元01、控件判断单元02、控件覆盖判断单元03、控件滑动判断单元04和子控件获取单元05；其中，控件获取单元01用于当用户使用移动设备切换不同的应用或者在同一应用的不同界面进行切换或滑动应用中的界面时，开始获取用户界面中的根节点控件；控件判断单元02用于判断当前控件是否可点击或是否能有子控件，如是，获取当前控件的长度、宽度以及在屏幕中的位置；否则，不再对当前控件进行判断；控件覆盖判断单元03用于判断当前控件是否被透明触发区域覆盖，如是，将当前控件标记为被透明触发区域覆盖并可点击；否则，不再对当前控件进行判断；控件滑动判断单元04用于判断当前控件是否可滑动，如是，同时将当前控件标记为被透明触发区域覆盖并可滑动；否则，获取下一个子控件；子控件获取单元05用于获取下一个子控件。
本实施例中，可点击控件判断单元4进一步包括遍历模块41和可点击控件存在判断模块42；其中，遍历模块41用于根据点击事件发生的坐标位置，遍历透明触发区域所覆盖的用户界面；可点击控件存在判断模块42用于判断是否存在能接收点击事件的可点击控件，如是，使用Android的辅助服务的performAction方法将点击事件传递给可点击控件；否则，丢弃点击事件。
本实施例中，滑动控件判断单元6进一步包括可滑动控件存在判断模块61和传递模块62；其中，可滑动控件存在判断模块61用于在用户界面中，判断在对应于滑动事件发生的坐标区域内是否存在能接收滑动事件的可滑动控件，如是，将滑动事件传递给可滑动控件；否则，丢弃滑动事件；传递模块62用于使用Android的辅助服务的performAction方法将滑动事件传递给可滑动控件。
总之，在本实施例中，在触发动作未能达到打开应用的条件时，通过将用户的滑动事件或点击事件下传到L型透明触发区域或反L型透明触发区域所覆盖的用户界面中，这样就能避免对用户正常使用移动设备造成干扰，大大增强了用户的体验。
以上所述仅为本发明的较佳实施例而已，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
Claims (1)
- 1、一种移动设备用户界面的实现方法，其特征在于，包括如下步骤：A）检测移动设备上是否有触发动作，如是，执行步骤B）；否则，继续进行本步骤的判断；B）判断所述触发动作是点击动作还是滑动动作，如是点击动作，则执行步骤C）；如是滑动动作，则执行步骤E）；C）判断是否可以通过点击打开应用，如是，打开应用，执行步骤G）；否则，执行步骤D）；D）判断用户界面对应点击事件的坐标处是否有可点击控件，如是，点击所述可点击控件，执行步骤G）；否则，丢弃所述点击事件，执行步骤G）；E）判断所述滑动动作的速度或角度是否达到预设阈值，如是，打开应用，执行步骤G）；否则，执行步骤F）；F）判断用户界面相应滑动事件区域是否有可滑动控件，如是，滑动所述可滑动控件，执行步骤G）；否则，丢弃所述滑动事件，执行步骤G）；G）结束本次操作。2、根据权利要求1所述的移动设备用户界面的实现方法，其特征在于，所述移动设备的屏幕上设有透明触发区域，所述透明触发区域用以检测对所述移动设备的触发动作，在所述步骤A）之前还包括预处理步骤：A01）当用户使用移动设备切换不同的应用或者在同一应用的不同界面进行切换或滑动应用中的界面时，开始获取用户界面中的根节点控件；A02）判断当前控件是否可点击或是否有子控件，如是，获取所述当前控件的长度、宽度以及在所述屏幕中的位置，执行步骤A03）；否则，不再对所述当前控件进行判断；A03）判断所述当前控件是否被所述透明触发区域覆盖，如是，将所述当前控件标记为被透明触发区域覆盖并可点击，执行步骤A04）；否则，不再对所述当前控件进行判断；A04）判断所述当前控件是否可滑动，如是，同时将所述当前控件标记为被透明触发区域覆盖并可滑动，执行步骤A05）；否则，执行步骤A05）；A05）获取下一个子控件，并返回步骤A02）。3、根据权利要求2所述的移动设备用户界面的实现方法，其特征在于，所述步骤D）进一步包括：D1）根据点击事件发生的坐标位置，遍历所述透明触发区域所覆盖的用户界面；D2）判断是否存在能接收所述点击事件的可点击控件，如是，使用Android的辅助服务的performAction方法将所述点击事件传递给所述可点击控件，执行步骤G）；否则，丢弃所述点击事件，执行步骤G）。4、根据权利要求2或3所述的移动设备用户界面的实现方法，其特征在于，所述步骤F）进一步包括：F1）在用户界面中，判断在对应于滑动事件发生的坐标区域内是否存在能接收滑动事件的可滑动控件，如是，执行步骤F2）；否则，丢弃所述滑动事件，执行步骤G)；F2）使用Android的辅助服务的performAction方法将所述滑动事件传递给所述可滑动控件，执行步骤G）。5、根据权利要求2所述的移动设备用户界面的实现方法，其特征在于，所述透明触发区域包括L型透明触发区域和反L型透明触发区域，所述L型透明触发区域位于屏幕的左下侧，所述反L型透明触发区域位于所述屏幕的右下侧。6、根据权利要求5所述的移动设备用户界面的实现方法，其特征在于，所述L型透明触发区域划分为多个小区域，每个所述小区域均有一个标识，当用户在所述L型触发区域上进行操作时，移动设备获取用户在所述L型触发区域上的操作数据，并将所述操作数据上传到云端服务器，所述云端服务器对接收的操作数据进行分析，生成所述L型触发区域的配置数据，所述移动设备定期从所述云端服务器获取所述配置数据，并依据所述配置数据动态调整所述每个小区域的宽度；所述预设阈值来自所述云端服务器。7、根据权利要求6所述的移动设备用户界面的实现方法，其特征在于，所述配置数据包括小区域标识、应用包名、Activity类名、小区域宽度、小区域内滑动速度阈值和角度范围。8、一种实现如权利要求1所述的移动设备用户界面的实现方法的装置，其特征在于，包括：触发检测单元：用于检测移动设备上是否有触发动作；触发动作判断单元：用于判断所述触发动作是点击动作还是滑动动作；点击判断单元：用于判断是否可以通过点击打开应用，如是，打开应用；否则，判断用户界面对应点击事件的坐标处是否有可点击控件；可点击控件判断单元：用于判断用户界面对应点击事件的坐标处是否有可点击控件，如是，点击所述可点击控件；否则，丢弃所述点击事件；滑动动作判断单元：用于判断所述滑动动作的速度或角度是否达到预设阈值，如是，打开应用；否则，判断用户界面相应滑动事件区域是否有可滑动控件；滑动控件判断单元：用于判断用户界面相应滑动事件区域是否有可滑动控件，如是，滑动所述可滑动控件；否则，丢弃所述滑动事件；结束单元：用于结束本次操作。9、根据权利要求8所述的装置，其特征在于，所述移动设备的屏幕上设有透明触发区域，所述透明触发区域用以检测对所述移动设备的触发动作，所述装置还包括：控件获取单元：用于当用户使用移动设备切换不同的应用或者在同一应用的不同界面进行切换或滑动应用中的界面时，开始获取用户界面中的根节点控件；控件判断单元：用于判断当前控件是否可点击或是否有子控件，如是，获取所述当前控件的长度、宽度以及在所述屏幕中的位置；否则，不再对所述当前控件进行判断；控件覆盖判断单元：用于判断所述当前控件是否被所述透明触发区域覆盖，如是，将所述当前控件标记为被透明触发区域覆盖并可点击；否则，不再对所述当前控件进行判断；控件滑动判断单元：用于判断所述当前控件是否可滑动，如是，同时将所述当前控件标记为被透明触发区域覆盖并可滑动；否则，获取下一个子控件；子控件获取单元：用于获取下一个子控件。10、根据权利要求9所述的装置，其特征在于，所述可点击控件判断单元进一步包括：遍历模块：用于根据点击事件发生的坐标位置，遍历所述透明触发区域所覆盖的用户界面；可点击控件存在判断模块：用于判断是否存在能接收所述点击事件的可点击控件，如是，使用Android的辅助服务的performAction方法将所述点击事件传递给所述可点击控件；否则，丢弃所述点击事件。11、根据权利要求9或10所述的装置，其特征在于，所述滑动控件判断单元进一步包括：可滑动控件存在判断模块：用于在用户界面中，判断在对应于滑动事件发生的坐标区域内是否存在能接收滑动事件的可滑动控件，如是，将滑动事件传递给所述可滑动控件；否则，丢弃所述滑动事件；传递模块：用于使用Android的辅助服务的performAction方法将所述滑动事件传递给所述可滑动控件。12、根据权利要求10所述的装置，其特征在于，所述透明触发区域包括L型透明触发区域和反L型透明触发区域，所述L型透明触发区域位于屏幕的左下侧，所述反L型透明触发区域位于所述屏幕的右下侧。13、根据权利要求12所述的移动设备用户界面的实现方法，其特征在于，所述L型透明触发区域划分为多个小区域，每个所述小区域均有一个标识，当用户在所述L型触发区域上进行操作时，移动设备获取用户在所述L型触发区域上的操作数据，并将所述操作数据上传到云端服务器，所述云端服务器对接收的操作数据进行分析，生成所述L型触发区域的配置数据，所述移动设备定期从所述云端服务器获取所述配置数据，并依据所述配置数据动态调整所述每个小区域的宽度；所述预设阈值来自所述云端服务器。14、根据权利要求13所述的移动设备用户界面的实现方法，其特征在于，所述配置数据包括小区域标识、应用包名、Activity类名、小区域宽度、小区域内滑动速度阈值和角度范围。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2015/078579 WO2016179752A1 (zh) | 2015-05-08 | 2015-05-08 | 一种移动设备用户界面的实现方法及装置 |
| CN201580006080.4A CN106030489B (zh) | 2015-05-08 | 2015-05-08 | 一种移动设备用户界面的实现方法及装置 |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2015/078579 WO2016179752A1 (zh) | 2015-05-08 | 2015-05-08 | 一种移动设备用户界面的实现方法及装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016179752A1 true WO2016179752A1 (zh) | 2016-11-17 |
Family
ID=57082502
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2015/078579 WO2016179752A1 (zh) | 2015-05-08 | 2015-05-08 | 一种移动设备用户界面的实现方法及装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106030489B (zh) |
| WO (1) | WO2016179752A1 (zh) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107291462A (zh) * | 2017-06-13 | 2017-10-24 | 成都四方伟业软件股份有限公司 | 交互式数据系统自定义编排方法、系统及编译、运行方法 |
| CN108021494A (zh) * | 2017-12-27 | 2018-05-11 | 广州优视网络科技有限公司 | 一种应用操作的录制方法、回放方法和相应装置 |
| CN110795175A (zh) * | 2018-08-02 | 2020-02-14 | Tcl集团股份有限公司 | 模拟控制智能终端的方法、装置及智能终端 |
| US20220342525A1 (en) * | 2019-07-19 | 2022-10-27 | Boe Technology Group Co., Ltd. | Pushing device and method of media resource, electronic device and storage medium |
| CN111399723A (zh) * | 2020-04-26 | 2020-07-10 | Oppo广东移动通信有限公司 | 一种设置项处理方法、装置及计算机可读存储介质 |
| CN112947747A (zh) * | 2021-02-02 | 2021-06-11 | 深圳市江元科技(集团)有限公司 | 一种手势导航的操作方法、装置、终端设备和存储介质 |
| CN112799656B (zh) * | 2021-04-15 | 2021-11-05 | 智道网联科技(北京)有限公司 | 自动化操作的脚本文件配置方法、装置、设备和存储介质 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102830914A (zh) * | 2012-07-31 | 2012-12-19 | 北京三星通信技术研究有限公司 | 操作终端设备的方法及其设备 |
| CN103226446A (zh) * | 2013-05-16 | 2013-07-31 | 北京奇虎科技有限公司 | 用于移动设备的用户界面的事件响应方法及移动设备 |
| CN104238794A (zh) * | 2013-06-24 | 2014-12-24 | 腾讯科技（深圳）有限公司 | 一种对触屏操作的响应方法及终端、移动终端 |
| US20150020191A1 (en) * | 2012-01-08 | 2015-01-15 | Synacor Inc. | Method and system for dynamically assignable user interface |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102662506A (zh) * | 2012-03-07 | 2012-09-12 | 中兴通讯股份有限公司 | 一种终端触控方法及终端 |
| KR101315957B1 (ko) * | 2012-05-21 | 2013-10-08 | 엘지전자 주식회사 | 이동 단말기 및 그 제어방법 |
| KR102105460B1 (ko) * | 2013-06-14 | 2020-06-01 | 엘지전자 주식회사 | 이동 단말기 및 그것의 제어방법 |
-
2015
- 2015-05-08 CN CN201580006080.4A patent/CN106030489B/zh not_active Expired - Fee Related
- 2015-05-08 WO PCT/CN2015/078579 patent/WO2016179752A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150020191A1 (en) * | 2012-01-08 | 2015-01-15 | Synacor Inc. | Method and system for dynamically assignable user interface |
| CN102830914A (zh) * | 2012-07-31 | 2012-12-19 | 北京三星通信技术研究有限公司 | 操作终端设备的方法及其设备 |
| CN103226446A (zh) * | 2013-05-16 | 2013-07-31 | 北京奇虎科技有限公司 | 用于移动设备的用户界面的事件响应方法及移动设备 |
| CN104238794A (zh) * | 2013-06-24 | 2014-12-24 | 腾讯科技（深圳）有限公司 | 一种对触屏操作的响应方法及终端、移动终端 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106030489A (zh) | 2016-10-12 |
| CN106030489B (zh) | 2019-11-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016179752A1 (zh) | 一种移动设备用户界面的实现方法及装置 | |
| WO2020233077A1 (zh) | 系统服务的监控方法、装置、设备及存储介质 | |
| WO2015012441A1 (en) | Digital device and control method thereof | |
| WO2012159290A1 (zh) | 电容式多点触摸屏基准数据更新的方法及系统 | |
| WO2020155358A1 (zh) | 智能家居设备联动控制方法、装置及智能家居设备 | |
| WO2018072567A1 (zh) | 移动终端基于指纹识别的紧急求救方法及系统、移动终端 | |
| WO2014040440A1 (zh) | 移动终端的操作方法及操作系统 | |
| WO2019103212A1 (ko) | 통신망을 이용한 선박내 ＩｏＴ 스마트 단말의 모니터링 시스템 | |
| WO2020224246A1 (zh) | 基于区块链的数据管理方法、装置、设备和存储介质 | |
| WO2019078489A1 (ko) | 사물 인터넷 플랫폼 서비스 제공 방법 및 서버장치 | |
| WO2020015060A1 (zh) | 用电量异常评估方法、装置、设备和计算机存储介质 | |
| WO2019024485A1 (zh) | 数据共享方法、装置及计算机可读存储介质 | |
| WO2020133764A1 (zh) | 语音遥控方法、系统、受控装置及计算机可读存储介质 | |
| WO2014139296A1 (zh) | 危险信息通知方法、装置及计算机可读存储介质 | |
| WO2016004671A1 (zh) | 一种信息分享方法及终端 | |
| WO2015058443A1 (zh) | 一种实现浏览器中光标定位的方法及装置 | |
| WO2020073494A1 (zh) | 网页后门检测方法、设备、存储介质及装置 | |
| WO2014077458A1 (ko) | 통신망의 종류를 구분하는 방법 및 이를 이용한 콘텐츠 제공 방법 | |
| WO2014178507A1 (en) | Display apparatus and searching method | |
| WO2017211056A1 (zh) | 一种移动终端的单手操作方法、及系统 | |
| WO2016155284A1 (zh) | 一种终端的信息采集方法及其终端 | |
| WO2014042476A1 (ko) | 지문을 이용한 파일 관리 방법, 사용자 단말기 및 기록 매체 | |
| WO2018076890A1 (zh) | 数据备份的方法、装置、存储介质、服务器及系统 | |
| WO2020019405A1 (zh) | 数据库监控方法、装置、设备及可读存储介质 | |
| WO2013122362A1 (ko) | 무선 네트워크 부하 저감 정책 운영 방법 및 시스템과 기록매체 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15891455 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 15891455 Country of ref document: EP Kind code of ref document: A1 |