CN107168600B - Push message checking method and device - Google Patents
Push message checking method and device Download PDFInfo
- Publication number
- CN107168600B CN107168600B CN201610128118.1A CN201610128118A CN107168600B CN 107168600 B CN107168600 B CN 107168600B CN 201610128118 A CN201610128118 A CN 201610128118A CN 107168600 B CN107168600 B CN 107168600B
- Authority
- CN
- China
- Prior art keywords
- digital identifier
- digital
- application
- aiming
- push message
- 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
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/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
-
- 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/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/0486—Drag-and-drop
Abstract
The application provides a push message viewing method and a push message viewing device, wherein the method comprises the following steps: monitoring a trigger event of a first digital identifier output on an icon aiming at a first application; the first number identifies a number of pieces of a push message to prompt for the first application; and when a first preset trigger event aiming at the first digital identifier is monitored, displaying the push message aiming at the first application in a preview interface. The method and the device can check the push messages more intuitively, and the checking efficiency of the push messages is improved.
Description
Technical Field
The present application relates to the field of communications, and in particular, to a push message viewing method and apparatus.
Background
At present, the APP in the mobile phone system usually receives various push messages pushed by the server, and after the APP receives the push messages, a digital identifier is usually displayed on an icon of the APP to prompt the number of the received push messages. When viewing the push message, the user can view the push message through a message center of the APP, or enter the APP to view the push message. However, the push messages are checked through the two ways, and the problem that the checking efficiency is not high enough exists.
Disclosure of Invention
The application provides a push message checking method, which comprises the following steps:
monitoring a trigger event of a first digital identifier output on an icon aiming at a first application; the first number identifies a number of pieces of a push message to prompt for the first application;
and when a first preset trigger event aiming at the first digital identifier is monitored, displaying the push message aiming at the first application in a preview interface.
Optionally, before displaying the push message for the first application in a preview interface when the first preset trigger event for the first digital identifier is monitored, the method further includes:
determining whether a selected event for the first digital identification has been heard;
and when a selected event aiming at the first digital identifier is monitored, highlighting the digital identifier and the icon of the first application on the desktop of the system.
Optionally, the method further includes:
when selected events aiming at the first digital identifiers are monitored, icons of all the applications outputting the digital identifiers on the system desktop are highlighted, and the digital identifiers output on the icons of the applications are highlighted on the system desktop.
Optionally, the first preset trigger event includes a drag event;
the displaying the push message for the first application in a preview interface comprises:
judging whether the first digital identifier is dragged to a second digital identifier output on an icon of a second application or not;
if the first digital identifier is not dragged to the position above the second digital identifier, outputting a preview interface on a system desktop, and displaying a push message aiming at the first application in the preview interface; or
And when a second preset trigger event aiming at the first digital identifier is monitored, outputting a preview interface on a system desktop and displaying the push message aiming at the first application in the preview interface.
Optionally, the outputting a preview interface on the system desktop includes:
judging whether the dragging distance for the first digital identifier reaches a threshold value;
and when the dragging distance for the first digital identifier reaches a threshold value, outputting the preview interface on a system desktop.
Optionally, the method further includes:
if the first digital identifier is dragged to the second digital identifier, merging and displaying the push message aiming at the first application and the push message aiming at the second application in the preview interface; alternatively, the first and second electrodes may be,
and when a second preset trigger event aiming at the first digital identifier is monitored, merging and displaying the push message aiming at the first application and the push message aiming at the second application in the preview interface.
Optionally, the second preset trigger event includes a long press event or a release event.
Optionally, the method further includes:
if the first digital identifier is dragged to the second digital identifier, combining the first digital identifier and the second digital identifier to obtain a third digital identifier;
and the numerical value of the third numerical identifier is the sum of the numerical value of the first numerical identifier and the numerical value of the second numerical identifier.
Optionally, the method further includes:
after the push message for the first application is displayed in the preview interface, clearing the first digital identifier;
and after the push message aiming at the first application and the push message aiming at the second application are merged and displayed in the preview interface, clearing the third digital identification.
The present application further provides a viewing apparatus for push messages, the apparatus including:
the monitoring module is used for monitoring a trigger event of a first digital identifier output on an icon aiming at a first application; the first number identifies a number of pieces of a push message to prompt for the first application;
and the display module is used for displaying the push message aiming at the first application in a preview interface when a first preset trigger event aiming at the first digital identifier is monitored.
Optionally, the monitoring module is further configured to:
before monitoring a first preset trigger event aiming at the first digital identifier, judging whether a selected event aiming at the first digital identifier is monitored; and when a selected event aiming at the first digital identifier is monitored, highlighting the digital identifier and the icon of the first application on the desktop of the system.
Optionally, the monitoring module is further configured to:
when selected events aiming at the first digital identifiers are monitored, icons of all the applications outputting the digital identifiers on the system desktop are highlighted, and the digital identifiers output on the icons of the applications are highlighted on the system desktop.
Optionally, the first preset trigger event includes a drag event;
the display module is specifically configured to:
judging whether the first digital identifier is dragged to a second digital identifier output on an icon of a second application or not;
if the first digital identifier is not dragged to the position above the second digital identifier, outputting a preview interface on a system desktop, and displaying a push message aiming at the first application in the preview interface; or
And when a second preset trigger event aiming at the first digital identifier is monitored, outputting a preview interface on a system desktop and displaying the push message aiming at the first application in the preview interface.
Optionally, the display module is specifically configured to:
judging whether the dragging distance for the first digital identifier reaches a threshold value;
and when the dragging distance for the first digital identifier reaches a threshold value, outputting the preview interface on a system desktop.
Optionally, the display module is further configured to:
if the first digital identifier is dragged to the second digital identifier, merging and displaying the push message aiming at the first application and the push message aiming at the second application in the preview interface; alternatively, the first and second electrodes may be,
and when a second preset trigger event aiming at the first digital identifier is monitored, merging and displaying the push message aiming at the first application and the push message aiming at the second application in the preview interface.
Optionally, the second preset trigger event includes a long press event or a release event.
Optionally, the display module is further configured to:
if the first digital identifier is dragged to the second digital identifier, combining the first digital identifier and the second digital identifier to obtain a third digital identifier;
and the numerical value of the third numerical identifier is the sum of the numerical value of the first numerical identifier and the numerical value of the second numerical identifier.
Optionally, the apparatus further comprises:
the clearing module is used for clearing the first digital identifier after the push message aiming at the first application is displayed in the preview interface; and clearing the third digital identifier after the push message aiming at the first application and the push message aiming at the second application are merged and displayed in the preview interface.
In the application, the interactive mode for quickly viewing the push message is provided by monitoring the trigger event of the digital identifier output on the icon aiming at the application and displaying the push message aiming at the application in the preview interface when the preset trigger event aiming at the digital identifier is monitored, so that the digital identifier output on the application icon can be directly triggered, namely, the push message aiming at the application can be quickly viewed in the desktop of the system where the application icon is located, the push message can be viewed more intuitively, and the viewing efficiency of the push message is improved.
Drawings
Fig. 1 is a flowchart of a push message viewing method according to an embodiment of the present application;
FIG. 2 is an interaction diagram of a quick look push message according to an embodiment of the present application;
fig. 3 is a flowchart of outputting a preview interface and displaying a push message of a current APP in the preview interface according to an embodiment of the present application;
FIG. 4 is an interaction diagram of another quick look push message provided by an embodiment of the present application;
FIG. 5 is an interaction diagram of another quick look push message provided by an embodiment of the present application;
FIG. 6 is a logic block diagram of a push message viewing device according to an embodiment of the present application;
fig. 7 is a hardware structure diagram of a terminal carrying the viewing apparatus for push messages according to an embodiment of the present application.
Detailed Description
In the related art, when an APP (Application) in a terminal system receives various push messages pushed by a server, a numeric identifier is usually displayed on an icon (for example, the upper right corner) of the APP to indicate the number of the received push messages.
When viewing the push message received by the APP, the user can generally view the push message in a message center of the APP (such as a pull-down notification bar of the APP), or view the push message by clicking an icon of the APP to enter the APP.
On the one hand, when the user views the push messages in the message center of the APP, the push messages of all the APPs in the mobile phone system are usually displayed in the message center in a centralized manner, so that the viewing is not intuitive enough, and the push messages are easily ignored by the user. On the other hand, when the user enters the APP to check the push message by clicking the icon of the APP, the operation efficiency of checking the message is not high.
In view of this, the present application provides an interaction method for quickly viewing push messages, in which a trigger event of a digital identifier output on an icon for an application is monitored, and when a preset trigger event for the digital identifier is monitored, a push message for the application is displayed in a preview interface, so that the digital identifier output on the application icon can be directly triggered, that is, the push message for the application can be quickly viewed in a system desktop where the application icon is located, so that the push message can be viewed more intuitively, and the viewing efficiency of the push message is improved.
The present application is described below with reference to specific embodiments and specific application scenarios.
Referring to fig. 1, fig. 1 is a view method for viewing a push message, which is applied to a terminal and provided by an embodiment of the present application, and the method performs the following steps:
and step 102, when a first preset trigger event aiming at the first digital identifier is monitored, displaying a push message aiming at the first application in a preview interface.
The terminal can comprise an intelligent terminal; the intelligent terminal can be a touch screen mobile terminal or a non-touch screen intelligent terminal. For example, the smart terminal may include a user's smart phone, tablet; alternatively, the intelligent terminal may also include a PC computer of the user.
The trigger event may include a touch event and a mouse event. For example, when the terminal is a touch screen smart phone, the user may trigger the terminal to output the preview interface by touching the digital identifier. For another example, when the terminal is a non-touch PC computer, the user may operate the digital identifier through a mouse to trigger the terminal to output the preview interface.
In this example, when receiving a push message for an APP in the system pushed by the server, the terminal may output a digital identifier at a preset position (for example, an upper right corner) of an icon of the APP, so as to prompt the user that the APP receives the push message pushed by the server, and prompt the user of the number of push messages received this time through a specific numerical value of the digital identifier. For example, when the terminal receives N push messages for an APP, a digital identifier N may be output at the upper right corner of an icon of the APP to prompt the user that the APP has received the N push messages.
Of course, if the terminal receives the push message for multiple APPs in the system, which is pushed by the server, the digital identifiers may be output at the preset positions of the icons of the multiple APPs.
In this example, the digital identifier may be a digital identifier that is output by the terminal and can be operated independently of the APP icon, that is, in practical applications, the user may perform operations such as long pressing, moving, dragging, and the like on the digital identifier output on the APP icon without affecting the APP icon.
In an embodiment shown, in order to ensure that the digital identifier can operate independently from the icon of the APP, when the terminal outputs the digital identifier on the icon of the APP, an independent display layer (view) may be created for the digital identifier, where the independent display layer may be a layer different from the display layer where the icon of the APP is located, so that a user may perform long-time pressing, moving, dragging, and the like on the digital identifier by operating the layer of the digital identifier without affecting the icon of the APP.
Of course, in practical applications, in order to ensure that the digital identifier can be triggered independently of the APP icon, other ways may be used to create an independent display layer for the digital identifier, besides the above description.
For example, in practical applications, when the terminal outputs the digital identifier on the icon of the APP, an independent display control may be added to the icon of the APP, and then the digital identifier is output on the icon of the APP based on the display control, so that the user may perform independent operation on the display control, perform long-time pressing, moving, dragging, and the like on the digital identifier, without affecting the icon of the APP.
The following description is given as an example of creating an independent display layer for the above-mentioned digital identifier to ensure that the digital identifier can operate independently of the icon of the APP.
In this example, after the terminal outputs the digital identifier on the icon of each APP that receives the push message, the terminal may perform event monitoring on the system desktop where the APPs are located. When the terminal monitors a selected event of a display layer of a digital identifier (i.e., a first digital identifier) for any APP (i.e., a first application) in the system, the terminal may select the display layer of the digital identifier and start event monitoring for the display layer in the background.
Wherein, in one illustrated embodiment, the selected event may comprise a long press event.
The user can select the display layer of the number identifier by long-pressing the number identifier (including long-pressing with a finger or long-pressing with a mouse). When the display layer of the digital identifier is selected, a subsequent user may perform a separate operation with respect to the display layer. In this case, when the subsequent terminal monitors an event of the user for the system desktop, the monitored event is responded as an event for the display layer of the digital identifier.
Of course, if the display layer of the digital identifier is not selected, the subsequent user cannot perform a separate operation on the display layer. In this case, when the subsequent terminal monitors the event of the user for the system desktop, the monitored event is defaulted as the event for the system to respond.
For example, taking a drag event of a user as an example, assuming that the user wishes to drag (including dragging with a finger and dragging with a mouse) the digital identifier, when the user performs an operation, the user may first select a display layer of the digital identifier by long-pressing the digital identifier, and then perform a drag operation with respect to the digital identifier. When the terminal monitors the dragging event corresponding to the dragging operation of the user, the dragging event is used as the event of the display layer of the digital identifier selected by the user to respond, and the dragging operation aiming at the digital identifier can be normally finished at the moment.
On the contrary, if the user does not select the display layer of the digital identifier by long pressing in the process of dragging the digital identifier, when the terminal monitors the dragging event corresponding to the dragging operation of the user in the background, the terminal defaults the dragging event as the event for the system to respond, and executes the operation defined for the dragging event in the system. For example, the operation defined for the drag event in the system usually defaults to a page turning operation for the system desktop, and therefore, in this case, the user originally wants to drag the digital identifier, and the system erroneously responds to an operation for turning the page for the system desktop.
Therefore, before the user operates the display layer of the digital identifier, the user can select the display layer, so that the terminal can be prevented from performing wrong response to the operation of the user.
In this example, when the user selects the display layer of the digital identifier, that is, after the terminal monitors the selected event of the user for the display layer in the background, the terminal may also output a specific interactive prompt for the user to prompt the user that the display layer has been selected.
In one embodiment shown, after the terminal monitors a selected event of the user for the display layer in the background, the terminal may highlight the display layer; for example, the terminal may highlight the display layer of the digital identifier with a color different from the background color of the system desktop to prompt the user that the display layer has been selected by the user and the user may operate the display layer.
In another embodiment shown, after the terminal monitors a selected event of the user for the display layer in the background, the display layer can be popped up in the system desktop; for example, after the user selects the display layer of the digital identifier by long-pressing the digital identifier, when the terminal pops up the display layer selected by the user, the display layer may be suspended on the icon of the current APP to prompt the user that the display layer has been selected by the user, and the user may operate the display layer.
It should be noted that the two embodiments shown above can be combined in practical applications. For example, after the user selects the display layer of the digital identifier, the terminal may highlight the display layer and pop up the display layer in the system desktop.
In this example, the system desktop of the terminal may include a plurality of APPs that output digital identifiers, and for each APP that outputs a digital identifier, a user may operate a display layer of the digital identifier output by the user to trigger the terminal to output a preview interface to display a push message for the APP. At this time, all APPs that output digital identifiers in the system desktop are objects that the user can operate.
In this case, in order to prompt the APP which can be operated by the user in the system desktop to the user, after the terminal monitors a selected event of the display layer of the digital identifier output by the user on any APP on the system desktop at the background, the terminal may highlight the selected display layer or pop up the display layer in the system desktop, and at this time, the terminal may highlight all the icons of the APPs which output the digital identifiers in the system desktop so as to prompt the user of the APPs which can be operated currently.
For example, referring to fig. 2, after the terminal monitors a selected event of the user for a display layer of a digital identifier output on any APP in the background, the background of the system desktop may be set to be semi-transparent, and then icons of all APPs that output digital identifiers on the system desktop and digital identifiers output by the icons are highlighted using a color different from the background color of the current system desktop, so as to prompt the user that the user may currently operate for the APPs that are highlighted by the icons.
In this example, after the terminal starts event listening for the display layer of the digital identifier selected by the user in the background, whether to output the preview interface to the user may be determined based on the monitored trigger event for the display layer.
The trigger event may include a first preset trigger event, and when the terminal monitors the first preset trigger event for the display layer, the terminal may be triggered to output the preview interface, and display the push message for the current APP on the preview interface.
In one embodiment, the first preset trigger event may include a drag event.
After the user selects the display layer of the digital identifier of the APP, a dragging operation may be executed for the selected display layer to trigger the terminal to output the preview interface. When the terminal monitors the dragging event corresponding to the dragging operation in the background, the preview interface can be output, and then the received push message for the APP is displayed in the preview interface.
Referring to fig. 3, fig. 3 is a flowchart illustrating a processing procedure of outputting a preview interface and displaying a push message of a current APP in the preview interface when a terminal monitors a first preset trigger event for a display layer selected by a user.
In the following embodiments, the first preset trigger event is taken as a drag event as an example for explanation.
It should be noted that, in practical applications, the first preset trigger event may also be another type of event besides the drag event, and the following embodiment is only exemplary of the first preset trigger event as the drag event, and is not intended to limit the present invention.
In this example, the process flow shown in fig. 3 includes the following execution steps:
the first digital identifier is a digital identifier output on an APP icon currently selected by the user. The second application is that, of all APPs that output digital identifiers on the system desktop, except APPs selected by the user, the second digital identifier is a digital identifier output on the other APPs.
The digital identification output by other APPs has the same function as the digital identification output by the APP selected by the user, and the digital identification output by the other applications still corresponds to different display layers respectively with the icons of the other applications.
In this example, since the system desktop may include a plurality of APPs outputting digital identifiers, when dragging a selected digital identifier, the user may drag the selected digital identifier onto the digital identifiers output by other APPs.
In this case, after monitoring the dragging event for the digital identifier selected by the user, the terminal may obtain an operation focus of the dragging event in the dragging process, and then judge whether the currently selected digital identifier is dragged onto the digital identifier output by another APP by judging whether the operation focus falls into a display layer of the digital identifier output by the other APP, so as to determine whether the push message of the APP currently selected by the user needs to be merged with the push message of the other APP for display.
If the operation focus of the dragging event falls into the display layers of the digital identifiers output by other APPs in the dragging process, it can be determined that the digital identifier selected by the user is dragged onto the digital identifiers output by other APPs, and at this time, the terminal can only display the push message of the selected APP in the preview interface.
On the contrary, if the operation focus of the dragging event does not fall into the display layers of the digital identifiers output by other APPs, it may be determined that the digital identifier selected by the user is not dragged onto the digital identifiers output by other APPs, and at this time, the terminal may merge and display the push message of the APP selected by the user and the push message of the other APPs in the preview interface.
The operation focus may include a dragging track corresponding to the dragging event.
For example, when the terminal is a touch screen terminal, the terminal may monitor a drag event for a display layer of a digital identifier selected by a user, acquire a touch point of the monitored drag event, and then generate a drag trajectory based on the acquired touch point.
For another example, when the terminal is a non-touch screen terminal, the terminal may monitor a mouse event for a display layer selected by a user, and record a position of the mouse in real time to generate a dragging track of the mouse.
The dragging track can be a continuous track or a discontinuous track;
for example, when the user drags the display layer of the selected digital identifier, if the user does not pause in the dragging process and the finger does not leave the screen, the dragging track acquired by the terminal is a continuous and smooth dragging track. If the user pauses for multiple times in the dragging process although the finger does not leave the screen, and the dragging direction changes after each pause, the dragging track acquired by the terminal is a dragging track with different directions in multiple sections.
In this example, if the terminal determines that the digital identifier selected by the user is not dragged to a digital identifier output by another APP, the terminal may quickly check the push message of the single APP selected by the user at this time.
Referring to fig. 4, fig. 4 is an interaction diagram of a push message for quickly viewing a single APP selected by a user in this embodiment.
As shown in fig. 4, if the terminal determines that the digital identifier selected by the user is not dragged above the digital identifiers output by other APPs, the terminal may output a preview interface at this time, and only the push message of the currently selected APP is displayed in the interface.
When the terminal outputs the preview interface on the system desktop, the terminal can trigger by judging whether the dragging distance of the dragging event reaches a preset threshold value. For example, the terminal may preset a threshold of the dragging distance (the threshold may be customized according to a requirement), after the dragging event is monitored, it may be determined whether the dragging distance of the dragging event reaches the threshold, and if the dragging distance of the dragging event reaches the threshold, the terminal may determine that the dragging event is an effective event, and may normally respond to the dragging event, and output the preview interface on the system desktop.
When the terminal outputs a preview interface and displays the push message of the APP in the interface, different implementation modes can be provided under different interaction scenes.
1) Scene one
When the terminal determines that the digital identifier selected by the user is not dragged to the digital identifiers output by other APPs, the terminal can immediately output the preview interface at the moment and display the push message of the APP in the preview interface.
In this scenario, after the user drags the display layer of the selected digital identifier, the preview interface may be immediately output as long as the terminal monitors the dragging event and determines that the dragging event is an effective event (that is, the dragging distance reaches a preset threshold).
At this time, the terminal can no longer respond to the event of the user after the dragging is finished; for example, the events after the dragging of the user is ended generally include a long-press event and a release event; namely, after the user finishes dragging, no matter whether the user keeps long pressing by the finger without leaving the screen or releasing the mouse, or the user says that the finger leaves the screen or releases the mouse, the terminal does not respond any more at this moment.
2) Scene two
When the terminal determines that the digital identifier selected by the user is not dragged to the digital identifiers output by other APPs, the terminal can continue to monitor the event aiming at the display layer of the digital identifier selected by the user, and when a second preset trigger event aiming at the display layer is monitored, the preview interface is output, and the push message of the APP is displayed in the preview interface.
The second preset trigger event may include a long press event or a release event.
In an interactive scenario, the second preset trigger event may be a long-press event.
When the terminal determines that the digital identifier selected by the user is not dragged to the digital identifiers output by other APPs, the terminal can continue to monitor the event aiming at the display layer of the digital identifier selected by the user, and when the long-press event aiming at the display layer is monitored again, the preview interface is output again, and the push message of the APP is displayed in the preview interface.
In this scenario, after the user drags the display layer of the selected digital identifier, when the dragging is stopped, the user may trigger the terminal to output the preview interface by holding the long press (that is, the user's finger does not leave the screen, or does not release the mouse), and the push message of the APP is displayed in the preview interface.
3) Scene three
In another interaction scenario, the second preset trigger event may be a release event.
When the terminal determines that the digital identifier selected by the user is not dragged to the digital identifiers output by other APPs, the terminal can continue to monitor the event aiming at the display layer of the digital identifier selected by the user, and when the terminal monitors the release event aiming at the display layer selected by the user again, the terminal outputs the preview interface and displays the push message of the APP in the preview interface.
In this scenario, after the user drags the display layer of the selected digital identifier, when the dragging is stopped, the user may trigger the terminal to output the preview interface by releasing an event (i.e., a finger leaves the screen or releases the mouse), and display the push message of the APP in the preview interface.
It can be seen that, in the three scenarios shown above, when the user drags the display layer of the selected digital identifier, the user may trigger the terminal to output the preview interface by ensuring that the dragging track does not fall into the display layers of the digital identifiers output by other APPs, and view the push message of the APP alone, without viewing the push message in a message center or entering the APP to view the push message, so that the viewing efficiency of the push message can be improved.
In this example, if the terminal determines that the digital identifier selected by the user is not dragged to the digital identifiers output by other APPs, the terminal may merge and check the push message of the APP selected by the user and the push messages of the other APPs.
Referring to fig. 5, fig. 5 is a schematic diagram of interaction of push messages for quickly viewing multiple APPs according to this embodiment.
As shown in fig. 5, when the terminal determines that the digital identifier selected by the user is dragged onto the digital identifiers output by other APPs, the terminal may obtain the received push message for the other APPs, then output a preview interface, and combine and display the push message of the APP selected by the user and the push messages of the other APPs in the preview interface.
For example, as shown in fig. 5, assuming that the APP selected by the user is I, after the user drags the display layer of the digital identifier output by the APP, the dragging track falls into the display layer of the digital identifier output by F, and then when the terminal displays the push message in the preview interface, the terminal may merge 2 push messages of I and 3 push messages of F, and display them in the preview interface. At this point, a total of 5 push messages are displayed in the preview interface.
Of course, if the dragging track falls into the display layers of the numeral identifiers of C, F and H, respectively, when the terminal displays the push message in the preview interface, the push messages of 4 APPs such as I, C, F and H may be merged and displayed in the preview interface. At this time, the preview interface displays 14 push messages in total (fig. 5 only shows that the dragging track only falls into the display layer of the numerical identifier of the F output).
When the terminal outputs the preview interface and displays the push message of the APP and the push messages of other APPs in which the dragging track falls in the preview interface, different implementation modes can still be provided under different interaction scenes.
It should be noted that the specific scenario is the same as the implementation described in scenario one, scenario two, and scenario three described above, and therefore, no further description is given, and when implementing, a person skilled in the art may refer to the description of scenario one, scenario two, and scenario three described above.
In this example, when the terminal determines that the digital identifier selected by the user is dragged to a digital identifier output by another APP, the terminal may further update the value of the digital identifier output by the current APP.
Wherein, the updated numerical value of the digital identifier of the APP is the sum of the numerical value of the digital identifier of the APP and the numerical values of the digital identifiers of the other APPs into which the dragging track falls.
For example, please refer to fig. 5, it is assumed that the APP selected by the user is I, the value of the digital identifier output by I is 2, after the user drags the display layer of the digital identifier output by APP, the dragging track falls into the display layer of the digital identifier output by F, and the value of the digital identifier output by F is 3, so that when the terminal updates the value of the digital identifier of APP1, the updated value of the digital identifier of I is 5 which is the sum of the values of the digital identifiers output by I and E.
It can be seen that, in the above embodiment, when the user drags the selected display layer, the user may trigger the terminal to output the preview interface by dropping the dragging track into the display layer of the digital identifier output by other APPs, and perform combined display on the push message of the APP and the push message of the APP that falls,
under the condition, the user can drag the display layer of the digital identifier output by the selected APP and drop the dragging track into the display layers of the digital identifiers output by other APPs on the system desktop, so that the APP selected by the user in the system desktop and the push message of other APPs falling into the dragging track can be viewed in a centralized manner, the push message does not need to be viewed at the message center of each APP respectively or enter each APP to view the push message respectively, and the viewing efficiency of the push message can be improved.
In the above embodiment, the case where the user-selected digital identifier is not dragged onto the digital identifiers output by other APPs and the case where the user-selected digital identifier is dragged onto the digital identifiers output by other APPs are respectively described.
For the first case, if the digital identifier selected by the user is not dragged to the digital identifiers output by other APPs, the terminal may view the push message displayed in the preview interface after the push message of the APP is separately displayed in the preview interface. After the user finishes checking, the terminal can clear the digital identifier output by the APP.
For the second case, if the digital identifier selected by the user is dragged to the digital identifier output by another APP, the terminal merges and displays the push message of the APP and the push message of the other APP in the preview interface, and the user can view the push message displayed in the preview interface. After the user finishes checking, the terminal can completely clear the APP and the digital identifiers output by other APPs in which the dragging track falls.
Of course, if the number of push messages in the preview interface is too many, and all push messages cannot be displayed on the preview interface at one time, the preview interface may further be provided with a progress bar capable of sliding up and down, and when a user views the push messages, the user may view all the push messages by sliding the preview interface up and down.
In this embodiment, the closing mode of the preview interface output by the terminal is not particularly limited in the embodiment, and the setting may be performed according to the output timing of the preview interface.
For example, if the output timing of the preview interface is that the user triggers the terminal to output the preview interface by holding a long press (i.e., the finger does not leave the screen or release the mouse) after dragging the display layer for the selected digital identifier, the terminal may set the operation of closing the preview interface as a release operation, i.e., the user may leave the screen by the finger or release the mouse to close the preview interface. Of course, if the preview interface is closed by the release operation, when the user views the push message in the preview interface, the user cannot slide the progress bar of the preview interface up and down, so that all the push messages cannot be viewed under the condition that the preview interface cannot display all the push messages at one time.
For another example, if the output timing of the preview interface is that the user triggers the terminal to output the preview interface by releasing an event (i.e., a finger leaves the screen or releases the mouse) after dragging the selected display layer, the terminal may set the operation of closing the preview interface to an operation for any area on the system desktop other than the preview interface, that is, the user may trigger the terminal to close the preview interface by performing any operation, such as clicking, double clicking, etc., on the area on the system desktop other than the preview interface.
Of course, in addition to the above-listed examples in which the closing manner of the preview interface can be set according to the output timing of the preview interface, in an actual application, the terminal may set a time length threshold value to the preview interface. After the preview interface is output, the preview interface can be automatically closed after the display duration of the preview interface reaches the duration threshold; or, after the length of time that the preview interface is not operated reaches the length of time threshold, the preview interface may be automatically closed, which is not listed in this embodiment.
In the above embodiment, an interaction manner for quickly viewing the push message is provided, and by monitoring the trigger event of the digital identifier output on the icon for the application and displaying the push message for the application in the preview interface when the preset trigger event for the digital identifier is monitored, the digital identifier output on the icon for the application can be directly triggered, that is, the push message for the application can be quickly viewed in the desktop of the system where the icon for the application is located, so that the push message can be viewed more intuitively, and the viewing efficiency of the push message is improved.
Corresponding to the method embodiment, the application also provides an embodiment of the device.
Referring to fig. 6, the present application provides a viewing apparatus 60 for push messages, which is applied to a terminal; referring to fig. 7, a hardware architecture related to a terminal of the viewing device 60 for bearing the push message generally includes a CPU, a memory, a non-volatile memory, a network interface, an internal bus, and the like; taking a software implementation as an example, the viewing device 60 for push messages can be generally understood as a computer program loaded in a memory, and a logic device formed by combining software and hardware after a CPU runs, where the viewing device 60 includes:
a monitoring module 601, configured to monitor a trigger event of a first digital identifier output on an icon for a first application; the first number identifies a number of pieces of a push message to prompt for the first application;
a display module 602, configured to display, in a preview interface, a push message for the first application when a first preset trigger event for the first digital identifier is monitored.
In this example, the listening module 601 is further configured to:
before monitoring a first preset trigger event aiming at the first digital identifier, judging whether a selected event aiming at the first digital identifier is monitored; and when a selected event aiming at the first digital identifier is monitored, highlighting the digital identifier and the icon of the first application on the desktop of the system.
In this example, the listening module 601 is further configured to:
when selected events aiming at the first digital identifiers are monitored, icons of all the applications outputting the digital identifiers on the system desktop are highlighted, and the digital identifiers output on the icons of the applications are highlighted on the system desktop.
In this example, the first preset trigger event includes a drag event;
the display module 602 is specifically configured to:
judging whether the first digital identifier is dragged to a second digital identifier output on an icon of a second application or not;
if the first digital identifier is not dragged to the position above the second digital identifier, outputting a preview interface on a system desktop, and displaying a push message aiming at the first application in the preview interface; or
And when a second preset trigger event aiming at the first digital identifier is monitored, outputting a preview interface on a system desktop and displaying the push message aiming at the first application in the preview interface.
In this example, the display module 602 is specifically configured to:
judging whether the dragging distance for the first digital identifier reaches a threshold value;
and when the dragging distance for the first digital identifier reaches a threshold value, outputting the preview interface on a system desktop.
In this example, the display module 602 is further configured to:
if the first digital identifier is dragged to the second digital identifier, merging and displaying the push message aiming at the first application and the push message aiming at the second application in the preview interface; alternatively, the first and second electrodes may be,
and when a second preset trigger event aiming at the first digital identifier is monitored, merging and displaying the push message aiming at the first application and the push message aiming at the second application in the preview interface.
In this example, the second predetermined trigger event includes a long press event or a release event.
In this example, the display module 602 is further configured to:
if the first digital identifier is dragged to the second digital identifier, combining the first digital identifier and the second digital identifier to obtain a third digital identifier;
and the numerical value of the third numerical identifier is the sum of the numerical value of the first numerical identifier and the numerical value of the second numerical identifier.
In this example, the apparatus further comprises:
a clearing module 603, configured to clear the first digital identifier after the push message for the first application is displayed in the preview interface; and clearing the third digital identifier after the push message aiming at the first application and the push message aiming at the second application are merged and displayed in the preview interface.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A method for viewing a pushed message, the method comprising:
monitoring a trigger event of a first digital identifier output on an icon aiming at a first application; the first number identifies a number of pieces of a push message to prompt for the first application;
when a first preset trigger event aiming at the first digital identifier is monitored, judging whether the first digital identifier is dragged to a second digital identifier output on an icon of a second application; wherein the first preset trigger event comprises a drag event;
if the first digital identifier is not dragged to the second digital identifier, when a second preset trigger event aiming at the first digital identifier is monitored, a preview interface is output on a system desktop, and the push message aiming at the first application is displayed in the preview interface; the second preset trigger event comprises a long-time pressing event or a releasing event;
if the first digital identifier is dragged to the second digital identifier, when a second preset trigger event aiming at the first digital identifier is monitored, merging and displaying a push message aiming at the first application and a push message aiming at the second application in the preview interface, and merging the first digital identifier and the second digital identifier to obtain a third digital identifier; and the numerical value of the third numerical identifier is the sum of the numerical value of the first numerical identifier and the numerical value of the second numerical identifier.
2. The method of claim 1, wherein before displaying the push message for the first application in a preview interface upon listening to a first preset trigger event for the first digital identifier, further comprising:
determining whether a selected event for the first digital identification has been heard;
and when a selected event aiming at the first digital identifier is monitored, highlighting the first digital identifier and the icon of the first application on a system desktop.
3. The method of claim 2, further comprising:
when selected events aiming at the first digital identification are monitored, icons of all the applications outputting the digital identifications on the system desktop are highlighted, and the digital identifications output on the icons of the applications are highlighted on the system desktop.
4. The method of claim 1, wherein outputting the preview interface on a system desktop comprises:
judging whether the dragging distance for the first digital identifier reaches a threshold value;
and when the dragging distance for the first digital identifier reaches a threshold value, outputting the preview interface on a system desktop.
5. The method of claim 1, further comprising:
after the push message for the first application is displayed in the preview interface, clearing the first digital identifier;
and after the push message aiming at the first application and the push message aiming at the second application are merged and displayed in the preview interface, clearing the third digital identification.
6. A push message viewing device, the device comprising:
the monitoring module is used for monitoring a trigger event of a first digital identifier output on an icon aiming at a first application; the first number identifies a number of pieces of a push message to prompt for the first application;
the display module is used for judging whether the first digital identifier is dragged to a second digital identifier output on an icon of a second application when a first preset trigger event aiming at the first digital identifier is monitored; wherein the first preset trigger event comprises a drag event;
if the first digital identifier is not dragged to the second digital identifier, when a second preset trigger event aiming at the first digital identifier is monitored, a preview interface is output on a system desktop, and the push message aiming at the first application is displayed in the preview interface; the second preset trigger event comprises a long-time pressing event or a releasing event;
if the first digital identifier is dragged to the second digital identifier, when a second preset trigger event aiming at the first digital identifier is monitored, merging and displaying a push message aiming at the first application and a push message aiming at the second application in the preview interface, and merging the first digital identifier and the second digital identifier to obtain a third digital identifier; and the numerical value of the third numerical identifier is the sum of the numerical value of the first numerical identifier and the numerical value of the second numerical identifier.
7. The apparatus of claim 6, wherein the listening module is further configured to:
before monitoring a first preset trigger event aiming at the first digital identifier, judging whether a selected event aiming at the first digital identifier is monitored; and when a selected event aiming at the first digital identifier is monitored, highlighting the first digital identifier and the icon of the first application on a system desktop.
8. The apparatus of claim 7, wherein the listening module is further configured to:
when selected events aiming at the first digital identification are monitored, icons of all the applications outputting the digital identifications on the system desktop are highlighted, and the digital identifications output on the icons of the applications are highlighted on the system desktop.
9. The apparatus of claim 6, wherein the display module is specifically configured to:
judging whether the dragging distance for the first digital identifier reaches a threshold value;
and when the dragging distance for the first digital identifier reaches a threshold value, outputting the preview interface on a system desktop.
10. The apparatus of claim 6, further comprising:
the clearing module is used for clearing the first digital identifier after the push message aiming at the first application is displayed in the preview interface; and clearing the third digital identifier after the push message aiming at the first application and the push message aiming at the second application are merged and displayed in the preview interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610128118.1A CN107168600B (en) | 2016-03-07 | 2016-03-07 | Push message checking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610128118.1A CN107168600B (en) | 2016-03-07 | 2016-03-07 | Push message checking method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107168600A CN107168600A (en) | 2017-09-15 |
| CN107168600B true CN107168600B (en) | 2020-06-09 |
Family
ID=59849356
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610128118.1A Active CN107168600B (en) | 2016-03-07 | 2016-03-07 | Push message checking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107168600B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110099111A (en) * | 2019-04-26 | 2019-08-06 | 深圳智链物联科技有限公司 | A kind of display system and its display methods of PUSH message |
| CN111443844A (en) * | 2020-03-26 | 2020-07-24 | 维沃移动通信有限公司 | Information processing method and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104077183A (en) * | 2014-07-08 | 2014-10-01 | 广东欧珀移动通信有限公司 | Reminding and operating method and device for reading of new software message |
| CN104360791A (en) * | 2014-10-29 | 2015-02-18 | 深圳市中兴移动通信有限公司 | Method for clearing corner mark of application icon |
| CN104866225A (en) * | 2015-05-22 | 2015-08-26 | 上海斐讯数据通信技术有限公司 | Electronic device having touch display screen and control method therefor |
| CN105183271A (en) * | 2015-06-26 | 2015-12-23 | 努比亚技术有限公司 | Information processing method and device |
| CN105224207A (en) * | 2014-09-04 | 2016-01-06 | 维沃移动通信有限公司 | A kind of end application is every empty control method and mobile terminal |
| CN105260086A (en) * | 2015-11-06 | 2016-01-20 | 奇酷互联网络科技（深圳）有限公司 | Notice viewing method, notice viewing device and terminal |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005055034A1 (en) * | 2003-12-01 | 2005-06-16 | Research In Motion Limited | Previewing a new event on a small screen device |
| CN103135967B (en) * | 2011-11-25 | 2017-07-21 | 腾讯科技（深圳）有限公司 | Show the method and system of unread message |
| CN103970774B (en) * | 2013-01-30 | 2015-09-09 | 腾讯科技（深圳）有限公司 | Notification icon method for cleaning and device |
| CN104461238B (en) * | 2014-11-27 | 2017-07-25 | 广东欧珀移动通信有限公司 | A kind of application icon processing method and terminal |
| CN104777961A (en) * | 2015-04-13 | 2015-07-15 | 努比亚技术有限公司 | Mobile terminal and method and device for quickly arranging desktop icons of mobile terminal |
| CN104965639B (en) * | 2015-06-30 | 2019-06-28 | 努比亚技术有限公司 | The footmark management method and device of application icon |
-
2016
- 2016-03-07 CN CN201610128118.1A patent/CN107168600B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104077183A (en) * | 2014-07-08 | 2014-10-01 | 广东欧珀移动通信有限公司 | Reminding and operating method and device for reading of new software message |
| CN105224207A (en) * | 2014-09-04 | 2016-01-06 | 维沃移动通信有限公司 | A kind of end application is every empty control method and mobile terminal |
| CN104360791A (en) * | 2014-10-29 | 2015-02-18 | 深圳市中兴移动通信有限公司 | Method for clearing corner mark of application icon |
| CN104866225A (en) * | 2015-05-22 | 2015-08-26 | 上海斐讯数据通信技术有限公司 | Electronic device having touch display screen and control method therefor |
| CN105183271A (en) * | 2015-06-26 | 2015-12-23 | 努比亚技术有限公司 | Information processing method and device |
| CN105260086A (en) * | 2015-11-06 | 2016-01-20 | 奇酷互联网络科技（深圳）有限公司 | Notice viewing method, notice viewing device and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107168600A (en) | 2017-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6640909B2 (en) | Theme display method and related devices | |
| US11573688B2 (en) | Method, apparatus, and terminal for processing notification information | |
| US10554805B2 (en) | Information processing method, terminal, and computer-readable storage medium | |
| CN102981763B (en) | The method running application program under touch screen lock-out state | |
| CN105573740B (en) | Split screen display mode operation method and terminal | |
| JP6475258B2 (en) | Message display method for distinguishing and displaying extracted messages in chat window, mobile terminal and chat server performing the method | |
| CN108829314B (en) | Screenshot selecting interface selection method, device, equipment and storage medium | |
| CN107066188B (en) | A kind of method and terminal sending screenshot picture | |
| CN108762611B (en) | Application icon management method and device and readable storage medium | |
| CN108170342B (en) | Application program interface display method and device, terminal and readable storage medium | |
| WO2015106510A1 (en) | Screen splitting method and device for applications, intelligent terminal and storage medium | |
| CN106681584A (en) | Method for optimizing application display and terminal | |
| CN107329659B (en) | Permission setting method and device, electronic equipment and storage medium | |
| CN106302932A (en) | The method and apparatus checking log in communication terminal | |
| KR20160020486A (en) | Independent hit testing for touchpad manipulations and double-tap zooming | |
| CN107409157B (en) | Method and device for setting information to burn after reading through pressure | |
| CN107168600B (en) | Push message checking method and device | |
| JP6317433B2 (en) | Interface function analysis and display method, apparatus, and computer storage medium | |
| CN112256563A (en) | Android application stability testing method and device, electronic equipment and storage medium | |
| EP3364637B1 (en) | Method and apparatus for filtering object by means of pressure | |
| CN112578959B (en) | Content publishing method and device | |
| CN105117154A (en) | Application method of Android list view component | |
| CN107797716B (en) | Information display control method and mobile terminal | |
| CN107422943A (en) | Button Activiation method and device | |
| CN111782113B (en) | Display method, display device and computer-readable storage medium |
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 | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1244078 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200922 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200922 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right |