Data transmission method, electronic device and storage medium

Abstract

The present application provides a data transmission method, an electronic device and a storage medium. The method comprises: after an electronic device displays a thumbnail corresponding to a screenshot image or screen recording video, a user drags the thumbnail to a hot area of a target service and then lifts off a hand, such that the electronic device can transmit the screenshot image or the screen recording video to the target service. The data transmission method can conveniently transmit resource data between services, improving the use experience of users.

Description

Data transmission method, electronic device and storage medium Technical Field

[0001] The present application relates to the field of intelligent terminal devices, and in particular to a data transmission method, electronic device and storage medium. Background Art

[0002] In modern life, smart devices such as mobile phones have become indispensable daily tools. In addition to basic communication functions, mobile phones and other smart devices also provide many practical functions, such as screenshots and screen recording, making people's lives more convenient and intelligent.

[0003] Summary of the Invention

[0004] The present application provides a data transmission method, electronic device, and storage medium. In this method, a user drags a screenshot thumbnail or a screen recording video thumbnail to transfer the screenshot image or screen recording video corresponding to the thumbnail to other services, thereby realizing the convenient transmission of resource data between services.

[0005] In the first aspect, the present application provides a data transmission method. The method includes: the electronic device displays a first thumbnail corresponding to a screenshot image or a screen recording video at a first position in response to a first operation; the electronic device creates a second thumbnail at the first position in response to a second operation on the first thumbnail, and hides the first thumbnail, wherein the second thumbnail and the first thumbnail have the same image screen, and the second thumbnail is a draggable image; the electronic device moves in response to a third operation, the second thumbnail moves with the hand, the third operation acts on the second thumbnail, and the third operation is a drag operation that is continuous with the second operation; the electronic device drags the second thumbnail to the first area in response to the third operation and then releases the hand, transmits the screenshot image or screen recording video corresponding to the first thumbnail to the first business, and does not display the first thumbnail and the second thumbnail, wherein the first area is the hot zone corresponding to the first business.

[0006] For example, the first operation may be a screenshot operation or an operation to end screen recording. The screenshot operation may be, for example, tapping the screen with a knuckle, performing an air gesture, clicking a shortcut switch, pressing a combination of keys, etc. The operation to end screen recording may be, for example, clicking a shortcut switch, pressing a combination of keys, performing an air gesture, or performing voice control.

[0007] Exemplarily, the first position may be the lower left corner area of ​​the display screen.

[0008] Exemplarily, the second operation may be a long press operation with a finger, and the third operation may be an operation of dragging the second thumbnail with a finger.

[0009] Exemplarily, the first thumbnail may be the thumbnail view image mentioned below, and the second thumbnail may be the draggable thumbnail image mentioned below.

[0010] In this way, users can drag and drop screenshot thumbnails or screen recording video thumbnails to pass the screenshot images or screen recording videos corresponding to the thumbnails to other services. The operation is simple and convenient, and realizes the rapid transmission of resource data between services.

[0011] According to the first aspect, the first service is a service that allows receiving screenshot images or screen recording videos.

[0012] The first service may receive resource data transmitted by dragging and dropping. For example, the first service may be the global favorites service, note service, service registered in a designated application, etc. mentioned below.

[0013] According to the first aspect and any implementation method of the first aspect, the solution also includes: the electronic device drags the second thumbnail to the second area in response to the third operation and then releases the hand, moves the second thumbnail to the first position and does not display the second thumbnail, and redisplays the first thumbnail; wherein the second area is an area corresponding to the second business, and the second business is a business that does not allow receiving screenshot images or screen recording videos; or, the second area is a non-hot area.

[0014] Exemplarily, the second area is a desktop icon area or a desktop blank area.

[0015] Like this, when the user drags the thumbnail to the position that can not receive resource data and leaves hand, electronic equipment restores and displays the situation before the user drags the thumbnail.At this moment, the user can also trigger the dragging operation to the thumbnail again.

[0016] According to the first aspect and any one implementation method of the first aspect, the electronic device creates a second thumbnail at the first position, including: the electronic device resets the first thumbnail to the first position; the electronic device creates a DragShadowBuilder object with the first thumbnail as a parameter; wherein the second thumbnail is a DragShadow object generated by the DragShadowBuilder object; the electronic device creates a target data structure object, and the target data structure stores a uniform resource identifier of a screenshot image or a screen recording video; the electronic device uses the DragShadowBuilder object and the target data structure as calling parameters, and calls the target drag method to enable the drag function for the DragShadow object.

[0017] Exemplarily, the target dragging method is the startDragAndDrop method.

[0018] According to the first aspect and any implementation manner of the first aspect, the target data structure object is a ClipData object.

[0019] According to the first aspect and any one of the implementation methods of the first aspect, the electronic device does not display the first thumbnail after dragging the second thumbnail to the first area and releasing the hand, including: the electronic device monitors a first drag event for the second thumbnail, and the operation type of the first drag event is drag end; the electronic device inquires that the screenshot image or screen recording video has been transmitted and processed, and does not display the first thumbnail.

[0020] In this way, the electronic device monitors the user's drag operation on the second thumbnail and performs a corresponding response operation based on the type of the drag operation. When the user's drag operation type is drag end, the electronic device controls whether the resource data corresponding to the thumbnail has been transmitted and processed. If the resource data has been transmitted and processed, the electronic device no longer displays the thumbnail, for example, destroys the thumbnail.

[0021] According to the first aspect and any one of the implementation methods of the first aspect, the electronic device drags the second thumbnail to the second area and then releases the hand, and displays the first thumbnail, including: the electronic device monitors a second drag event for the second thumbnail, and the operation type of the second drag event is drag end; the electronic device queries that the screenshot image or screen recording video has not been transmitted and processed, and redisplays the first thumbnail.

[0022] When the user drag operation type is drag end, the electronic device determines whether the resource data corresponding to the thumbnail has been transmitted and processed. If the resource data has not been transmitted and processed, the electronic device redisplays the first thumbnail. At this time, the user can also trigger the drag operation on the thumbnail again.

[0023] According to the first aspect and any implementation of the first aspect, hiding the first thumbnail by the electronic device may include: the electronic device recording the original size of the first thumbnail and resetting the size of the first thumbnail to 0. Correspondingly, redisplaying the first thumbnail by the electronic device may include: the electronic device resetting the size of the first thumbnail to the recorded original size. In this way, the electronic device can achieve the effect of hiding or redisplaying the thumbnail by adjusting the thumbnail size.

[0024] According to the first aspect and any implementation of the first aspect, the electronic device sets the first thumbnail to be fully transparent. Correspondingly, the electronic device redisplays the first thumbnail, which may include: the electronic device sets the first thumbnail to be opaque. In this way, the electronic device can achieve the effect of hiding or redisplaying the thumbnail by adjusting the transparency of the thumbnail.

[0025] According to the first aspect and any implementation of the first aspect, the electronic device sets the visibility of the first thumbnail to invisible. Correspondingly, the electronic device redisplays the first thumbnail, which may include: the electronic device sets the visibility of the first thumbnail to visible. In this way, the electronic device can achieve the effect of hiding or redisplaying the thumbnail by adjusting the thumbnail visibility attribute.

[0026] According to the first aspect and any implementation manner of the first aspect, the method further includes: the electronic device generates a target frame at a first position in response to the second operation, and the target frame is used to indicate the starting drag area of ​​the second thumbnail; the electronic device drags the second thumbnail to the third area in response to the third operation, and hides the target frame; wherein, when the second thumbnail is located in the third area, there is no intersection between the second thumbnail and the target frame; the electronic device drags the second thumbnail to the fourth area in response to the third operation, and displays the target frame; wherein, when the second thumbnail is located in the fourth area, there is an intersection between the second thumbnail and the target frame.

[0027] For example, the target frame may be the frame view object mentioned below, as shown in frame 443 in Figures 4g and 4h. When the second thumbnail is dragged to a point where it does not intersect with the target frame, the target frame is not displayed; when the second thumbnail is dragged to a point where it intersects with the target frame, the target frame is displayed.

[0028] In this implementation, the target frame can be used to visually prompt the user, prompting the user to stop dragging the thumbnail in the frame area and release the thumbnail to cancel the thumbnail dragging operation.

[0029] According to the first aspect and any implementation manner of the first aspect, the method further includes: the electronic device drags the second thumbnail to the fourth area in response to the third operation and then releases the hand, moves the second thumbnail to the first position and does not display the second thumbnail, and redisplays the first thumbnail.

[0030] In this way, when the user drags the thumbnail to the intersection with the target image and then lets go, the electronic device restores the situation before the thumbnail is dragged. At this time, the user can also trigger the drag operation on the thumbnail again.

[0031] According to the first aspect and any one of the implementation methods of the first aspect, the electronic device drags the second thumbnail to the fourth area in response to the third operation and then releases the hand, and redisplays the first thumbnail, including: the electronic device monitors the third drag event on the second thumbnail, and the operation type of the third drag event is the end of drag; the electronic device queries that the screenshot image or the recorded video has not been transmitted and processed, and redisplays the first thumbnail.

[0032] When the user drag operation type is drag end, the electronic device determines whether the resource data corresponding to the thumbnail has been transmitted and processed. If the resource data has not been transmitted and processed, the electronic device redisplays the first thumbnail. At this time, the user can also trigger the drag operation on the thumbnail again.

[0033] According to the first aspect and any implementation of the first aspect, the electronic device, in response to a third operation, drags the second thumbnail to the third area and hides the target frame, including: the electronic device monitors a fourth drag event on the second thumbnail and sets the target frame to be fully transparent; wherein the operation type of the fourth drag event is leaving the frame area. Correspondingly, the electronic device drags the second thumbnail to the fourth area and displays the target frame, including: monitoring a fifth drag event on the second thumbnail and setting the target frame to be non-transparent; wherein the operation type of the fifth drag event is entering the frame area.

[0034] When the user drag operation type is to leave the frame area, the electronic device sets the target frame to be fully transparent to hide the target frame; when the user drag operation type is to enter the frame area, the electronic device sets the target frame to be non-fully transparent to unhide the target frame.

[0035] According to the first aspect and any one implementation manner of the first aspect, after displaying the first thumbnail corresponding to the screenshot image or screen recording video at the first position, the method also includes: the electronic device starts a target timing for the first thumbnail; wherein the target timing is used to trigger non-display of the first thumbnail when the timing duration reaches a preset duration; the electronic device monitors the sixth drag event for the second thumbnail, and cancels the target timing for the first thumbnail; wherein the operation type of the sixth drag event is drag start.

[0036] This implementation takes into account the existing solution of automatic disappearance timing of thumbnails. Among them, when the user starts dragging, the automatic disappearance timing of the thumbnail is canceled to avoid the thumbnail being destroyed due to the end of the timing during the user dragging the thumbnail.

[0037] According to the first aspect and any one implementation manner of the first aspect, after the electronic device redisplays the first thumbnail, the method further includes: the electronic device restarting the target timing for the first thumbnail.

[0038] In this implementation, if the user cancels the drag operation, or if the user completes the drag operation but the resource data corresponding to the thumbnail has not been processed, causing the electronic device to redisplay the corresponding thumbnail, the electronic device restarts the automatic disappearance timer for the thumbnail. Before the automatic disappearance timer expires, the user can trigger the drag operation on the thumbnail again.

[0039] According to the first aspect and any implementation manner of the first aspect, after the electronic device creates the second thumbnail at the first position, the method further includes: the electronic device moves the second thumbnail from the first position to the second position according to the position of the second operation; wherein, when the second thumbnail is at the second position, the position of the second operation is located in the central area of ​​the second thumbnail.

[0040] In this way, no matter where the user presses to trigger the movement of the thumbnail, the electronic device can automatically adjust the position of the thumbnail so that the user's pressing position is located in the center area of ​​the thumbnail, thereby improving the user's dragging experience.

[0041] In a second aspect, the present application provides an electronic device comprising a memory and a processor. The processor and the memory are coupled, and the memory stores program instructions. When the program instructions are executed by the processor, the electronic device performs the data transmission method of the first aspect and any one of the first aspects.

[0042] The second aspect and any implementation of the second aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the second aspect and any implementation of the second aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0043] In a third aspect, the present application provides a computer-readable medium for storing a computer program, wherein the computer program includes instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0044] The third aspect and any implementation of the third aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the third aspect and any implementation of the third aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0045] In a fourth aspect, the present application provides a computer program comprising instructions for executing the data transmission method of the first aspect and any one of the first aspects.

[0046] The fourth aspect and any implementation of the fourth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fourth aspect and any implementation of the fourth aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0047] In a fifth aspect, the present application provides a chip comprising a processing circuit and a transceiver pin. The transceiver pin and the processing circuit communicate with each other via an internal connection path, and the processing circuit executes the data transmission method of the first aspect and any one of the first aspects to control the receive pin to receive a signal and to control the transmit pin to send a signal.

[0048] The fifth aspect and any implementation of the fifth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fifth aspect and any implementation of the fifth aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] FIG1 is a schematic diagram showing a hardware structure of an electronic device;

[0050] FIG2 is a schematic diagram illustrating a software structure of an electronic device;

[0051] 3a to 3e are schematic diagrams illustrating exemplary application scenarios of the screen recording function and the screen capture function of an electronic device;

[0052] 4a and 4b are schematic diagrams illustrating exemplary data transmission scenarios based on dragging of screen recording video thumbnails;

[0053] FIG4c is a schematic diagram illustrating an exemplary data transmission scenario based on dragging a screen recording video thumbnail;

[0054] 4d to 4e are schematic diagrams illustrating exemplary data transmission scenarios based on dragging of screen recording video thumbnails;

[0055] FIG4f is a schematic diagram showing an exemplary scenario of dragging and resetting a screen recording video thumbnail;

[0056] Figures 4g to 4h are schematic diagrams of exemplary dragging of screen recording video thumbnails;

[0057] FIG5 is an interactive flowchart exemplarily illustrating a data transmission method based on dragging a screen recording video thumbnail;

[0058] FIG6 a is an exemplary flowchart of processing logic for starting a thumbnail drag;

[0059] FIG6 b is a schematic diagram showing an exemplary scenario of automatically adjusting the position of a draggable thumbnail image based on a user's pressing position;

[0060] FIG. 6 c is a flowchart illustrating an exemplary processing logic for responding to a user dragging a draggable thumbnail image. DETAILED DESCRIPTION

[0061] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0062] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0063] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, the terms "first target object" and "second target object" are used to distinguish different objects, rather than to describe a specific order of objects.

[0064] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0065] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

[0066] FIG1 shows a schematic diagram of the structure of an electronic device 100. It should be understood that the electronic device 100 shown in FIG1 is merely an example of an electronic device, and that the electronic device 100 may have more or fewer components than shown, may combine two or more components, or may have a different component configuration. The various components shown in FIG1 may be implemented in hardware, including one or more signal processing and / or application-specific integrated circuits, software, or a combination of hardware and software.

[0067] The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

[0068] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0069] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0070] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0071] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0072] It is understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is merely an illustrative illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0073] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device via the power management module 141.

[0074] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0075] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0076] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0077] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0078] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information. Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel.

[0079] The electronic device 100 can implement a camera function through an ISP, a camera 193, a video codec, a GPU, a display 194, and an application processor. The camera 193 is used to capture still images or videos. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than one.

[0080] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0081] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. This allows electronic device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0082] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0083] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. Exemplarily, in an embodiment of the present application, the processor 110 may implement the thumbnail-based data transmission method in an embodiment of the present application by running the instructions stored in the internal memory 121.

[0084] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0085] The pressure sensor is used to sense pressure signals and can convert pressure signals into electrical signals. In some embodiments, the pressure sensor can be set on the display screen 194. When force acts on the pressure sensor, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the touch operation intensity based on the pressure sensor. The electronic device 100 can also calculate the position of the touch based on the detection signal of the pressure sensor. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, the instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, the instruction to create a new short message is executed.

[0086] A touch sensor, also known as a "touch panel," can be provided on the display screen 194. The touch sensor and the display screen 194 form a touch screen, also known as a "touch screen." The touch sensor is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be provided on the surface of the electronic device 100, at a location different from that of the display screen 194.

[0087] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

[0088] For example, the software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the present application, the Android system with a layered architecture is used as an example to illustrate the software structure of the electronic device 100.

[0089] FIG2 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application.

[0090] The layered architecture of electronic device 100 divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other via software interfaces. In some embodiments, the Android system is divided into four layers: from top to bottom, the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0091] The application layer can include a series of application packages.

[0092] As shown in Figure 2, the application package may include a screenshot application, a screen recording application, a global favorites application, a gallery, a note application, etc. For example, the application package may also include call, calendar, map, navigation, music, video, short message, camera, WLAN, Bluetooth and other applications.

[0093] Among them, the screenshot / recording screen application can implement the thumbnail-based data transmission method in the embodiment of the present application, and the thumbnail can be a screenshot thumbnail or a screen recording video thumbnail. Exemplarily, in order to implement the thumbnail-based data transmission method in the embodiment of the present application, the screenshot / recording screen application may include a management module, a thumbnail view object, a long press listener (OnLongClickListener) object bound to the thumbnail view object, a frame view object, and a drag and drop listener (OnDragListener) object bound to the frame view object. Among them, the management module can be used to manage the life cycle of the thumbnail view object, the long press listener object, the frame view object, and the drag and drop listener object. The long press listener object is used to listen to the user's long press operation on the thumbnail view object, and the drag and drop listener object is used to listen to the user's drag operation, drag and drop operation, etc. on the draggable thumbnail image. In an optional embodiment, the drag and drop listener object can also be bound to other view objects, which is not limited in this embodiment.

[0094] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0095] As shown in FIG2 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0096] The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, etc. The view system can be used to build applications. The display interface can be composed of one or more views. For example, after the user takes a screenshot or ends screen recording, a thumbnail view object can be displayed in the display interface. In an embodiment of the present application, the view system can also be used to construct a draggable thumbnail image corresponding to the thumbnail view object, and to support the user's dragging operations, drag and drop operations, etc. on the draggable thumbnail image. Among them, the view system can also be used to implement the binding of the view object and the listener object, as well as to send the user's long press event of the thumbnail view object to the long press listener object, and send the user's drag event corresponding to the draggable thumbnail image to the drag and drop listener object.

[0097] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0098] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0099] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

[0100] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0101] The Notification Manager allows applications to display notifications in the status bar. These messages can be used to convey notifications and can disappear automatically after a short pause, without requiring user interaction. For example, notifications are used to notify the completion of downloads, message reminders, and so on. Notifications can also appear in the system's top status bar as icons or scrolling text, such as notifications from applications running in the background, or as dialog windows on the screen. Notifications can also take the form of text messages displayed in the status bar, beeping sounds, vibrations on electronic devices, or flashing indicator lights.

[0102] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0103] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0104] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0105] The system library can include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0106] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0107] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0108] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0109] A 2D graphics engine is a drawing engine for 2D drawings.

[0110] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, Wi-Fi drivers, sensor drivers, etc.

[0111] It is understood that the layers in the software structure shown in FIG2 and the components included in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown in the figure, and each layer may include more or fewer components, or some components may be combined, or some components may be separated, or the components may be arranged differently.

[0112] It is understandable that, in order to implement the data transmission method in the embodiment of the present application, the electronic device includes hardware and / or software modules that perform the corresponding functions. In combination with the algorithm steps of each example described in the embodiment disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of this application.

[0113] In addition to basic communication functions, smart terminals such as mobile phones also provide many practical functions, such as screenshot function, screen recording (abbreviated as screen recording) function, etc. When a user performs a screenshot operation on a mobile phone, the screenshot application will generate a screenshot image thumbnail and display the screenshot image thumbnail on the mobile phone interface. Similarly, when the user performs the screen recording end operation on the mobile phone, the screen recording application will generate a screen recording video thumbnail and display the screen recording video thumbnail on the mobile phone interface. Figures 3a to 3e exemplify some application scenarios related to screenshot image thumbnails or screen recording video thumbnails.

[0114] FIG3a exemplarily shows a schematic diagram of the scene of the generation and disappearance of the screen recording video thumbnail. Referring to FIG3a (1), exemplarily, after the mobile phone starts screen recording, the user performs a click operation in the screen recording prompt control 301 to end the screen recording. Optionally, the user can use methods such as clicking a shortcut switch, pressing a combination button, air gestures, voice control, etc. to end the screen recording, which is not limited in the embodiment of the present application. In response to the user's operation, the mobile phone ends the screen recording operation, saves the screen recording video, and generates a thumbnail 302 corresponding to the screen recording video, which is displayed on the mobile phone interface, as shown in FIG3a (2). After the screen recording video thumbnail 302 is displayed, the screen recording application starts an automatic disappearance timer for the screen recording video thumbnail 302 (the timer duration can be 3s, 5s, etc.). Before the automatic disappearance timer ends, if the user does not perform any operation on the screen recording video thumbnail 302, the mobile phone controls the screen recording video thumbnail 302 to automatically disappear in the mobile phone display interface, as shown in FIG3a (3).

[0115] FIG3b exemplarily shows a schematic diagram of the generation and disappearance of a screenshot image thumbnail. Referring to FIG3b (1), exemplarily, the user uses a knuckle to tap the mobile phone interface 311 to trigger the mobile phone screenshot. Optionally, the user can also use air gestures, click a shortcut switch, press a combination of keys, etc. to trigger the screenshot operation, which is not limited in the embodiment of the present application. In response to the user's operation, the mobile phone captures the image corresponding to the current display interface, saves the screenshot image, and generates a thumbnail 312 corresponding to the screenshot image, which is displayed on the mobile phone interface, as shown in FIG3b (2). After the screenshot image thumbnail 312 is displayed, the screenshot application starts the automatic disappearance timer for the screenshot image thumbnail 312 (the timer duration can be 3s, 5s, etc.). Before the automatic disappearance timer ends, if the user does not perform any operation on the screenshot image thumbnail 312, the mobile phone controls the screenshot image thumbnail 312 to automatically disappear from the mobile phone display interface, as shown in FIG3b (3).

[0116] FIG3c exemplifies a scenario of operating a screenshot image thumbnail. Taking a screenshot image thumbnail as an example, as shown in FIG3c (1), the user clicks on the screenshot image thumbnail 321. In response to the user operation, the mobile phone displays the screenshot image editing interface, as shown in FIG3c (2). In this editing interface, the user can edit, delete, and perform other operations on the screenshot image.

[0117] Taking the screenshot image thumbnail as an example, FIG3d exemplifies another scenario of operating the screenshot image thumbnail. Referring to FIG3d (1), the user swipes up the screenshot image thumbnail 331. In response to the user operation, the mobile phone displays a prompt message "Share" 332 at the top of the screenshot image thumbnail 331. When the user continues to swipe up and releases his hand (or releases his hand), the mobile phone displays the sharing interface of the screenshot image, which can be shown in FIG3d (3). In this sharing interface, the user can send the screenshot image 333 corresponding to the screenshot image thumbnail 331 to an application (such as Tik Tok, Pailitao, Memo, Email, etc.), and then the user can perform relevant operations on the screenshot image 333 through this application (such as sharing with friends, publishing to a platform, storing, printing, etc.).

[0118] Taking the screenshot image thumbnail as an example, FIG3e exemplifies another operation scenario for the screenshot image thumbnail. Referring to FIG3e (1), the user slides down the screenshot image thumbnail 341. In response to the user operation, the mobile phone displays a prompt message "Scrolling screenshot" 342 at the bottom of the screenshot image thumbnail 341. When the user continues to slide down and releases the hand, if the current interface of the mobile phone supports scrolling down, the current interface of the mobile phone scrolls down and performs the scrolling screenshot operation to obtain the corresponding long screenshot image.

[0119] For the screen recording video thumbnail, the user can also edit, delete, etc. by clicking it, or share it by swiping up, etc., which will not be described in detail in the embodiments of the present application.

[0120] The embodiment of the present application provides a data transmission method based on long pressing and dragging thumbnails (screenshot image thumbnails or screen recording video thumbnails), which is simple and convenient to operate, thereby improving the user experience. Among them, the user long presses and drags the thumbnail to the target application (or target hot zone) and releases the hand. In response to the user operation, the target application can receive the image or video corresponding to the thumbnail, thereby realizing the flow of resource data between applications. It should be pointed out that the target application refers to an application that can respond to data drag and drop transfer operations, such as a global collection application, a note application, etc.

[0121] In this way, after the screen recording is completed or the screenshot is taken, when the relevant thumbnail (screen recording video thumbnail or screenshot image thumbnail) is displayed on the mobile phone interface, the user can quickly transfer the resource data corresponding to the thumbnail to other applications or services by dragging the thumbnail on this user interface.

[0122] In order to help those skilled in the art better understand the data transmission method in the embodiment of the present application, the user operation method is introduced in conjunction with Figures 4a to 4f. In Figures 4a to 4f, the long press and drag of a recorded video thumbnail is used as an example to explain the situation.

[0123] As shown in (1) in FIG4a, after the screen recording is completed, the screen recording video thumbnail 401 is displayed in the mobile phone interface. The user long presses the screen recording video thumbnail 401. In response to the user operation, the screen recording video thumbnail 402 floats up, and the floating screen recording video thumbnail 402 can be dragged by the user. Among them, the "floating" of the screen recording video thumbnail is the user's visual experience of the screen recording video thumbnail following the manual effect (not shown in the figure), just like the screen recording video thumbnail "floating out" in the desktop interface. The manual effect is used to prompt the user to drag the screen recording video thumbnail, that is, to prompt the screen recording video thumbnail to move with the user's finger. In order to further enhance the user's experience, the manual effect can also include two parts of the dynamic effect. First, the screen recording video thumbnail is visually floated, and second, the position of the screen recording video thumbnail is moved so that the user's finger is located in the center area of ​​the screen recording video thumbnail (please refer to the relevant explanation of FIG6b below).

[0124] The "floating" effect can be achieved in a variety of ways, for example, it can be to scale the screen recording video thumbnail 402, add a shadow to the screen recording video thumbnail 402, and adjust the border of the screen recording video thumbnail 402, or it can be a combination of the above or other methods. In order to distinguish it from the non-floating screen recording video thumbnail 401 originally displayed in the mobile phone interface, in this embodiment, the screen recording video thumbnail that is floated and can be dragged by the user is called the screen recording video thumbnail 402, as shown in (2) in Figure 4a. Compared with the screen recording video thumbnail 401, the size, border, shadow, etc. of the screen recording video thumbnail 402 can be different (not shown in the figure). Continuing to refer to (3) and (4) in Figure 4a, the user can drag the screen recording video thumbnail 402 arbitrarily in the mobile phone display interface.

[0125] It should be pointed out that the "floating screen recording video thumbnails" mentioned in other figures below can all refer to the relevant explanations in the previous paragraph and will not be repeated hereafter.

[0126] In one implementation, when the target application is displayed in the form of a floating ball, it can respond to the operation of dragging and dropping data. The following example uses the user dragging a screen recording video thumbnail to the floating ball of a global favorite application to store the screen recording video corresponding to the screen recording video thumbnail in the global favorite application. It can be understood that the screen recording video corresponding to the screen recording video thumbnail is the screen recording video described by the screen recording video thumbnail.

[0127] Continuing with reference to (1) in FIG4b, when the user drags the screen recording video thumbnail 402, since the global collection application can respond to the operation of data drag and drop, the floating ball icon of the global collection application changes from the folded floating ball 403 (as shown in (1) in FIG4a) to the expanded floating ball 404. In order to prompt the user to operate, the expanded floating ball 404 displays the prompt message "Drag here". Continuing with reference to (2) in FIG4b, the user continues to drag the screen recording video thumbnail 402 to the floating ball of the global collection application. That is, the screen recording video thumbnail 402 is dragged to the hot zone corresponding to the floating ball of the global collection application. In response to the user's operation, the prompt message on the floating ball of the global collection application changes to "Raise your hand to collect", as shown in the expanded floating ball 405. After the user drags the screen recording video thumbnail 402 to the expanded floating ball 405, the user releases his hand (that is, his finger leaves the mobile phone display). In response to the user's hand-off operation, the screen recording video thumbnail 402 disappears in the interface (or is called undisplayed), and the mobile phone transfers the screen recording video corresponding to the screen recording video thumbnail 402 to the global collection application. The global collection application receives the screen recording video corresponding to the screen recording video thumbnail 402 and adds the screen recording video to the global collection application. The prompt message on the floating ball of the global collection application changes to "Collection successful", and you can refer to the expanded floating ball 406 displayed in the interface (3) in Figure 4b. At this point, the screen recording video corresponding to the screen recording video thumbnail 402 completes data transfer. That is, the user transfers the corresponding screen recording video to the global collection application by dragging the screen recording video thumbnail 402. At this time, the floating ball of the global collection application can be restored to the folded state, and you can refer to the folded floating ball 407 displayed in the interface (4) in Figure 4b. Since the screen recording video corresponding to the screen recording video thumbnail 402 has been collected in the global collection application, when the user clicks the application icon 408 of the global collection application and opens the global collection application, the user can view the screen recording video corresponding to the screen recording video thumbnail 402 in the relevant interface of the global collection application.

[0128] Optionally, when the global favorites app is not installed on the phone, if the user drags screen recording video thumbnail 402 into the hot zone range corresponding to the note application floating ball (or the hot zone range corresponding to the note application) and then releases the dragged video, in response to the user operation, the screen recording video corresponding to screen recording video thumbnail 402 is transferred to the note application, and screen recording video thumbnail 402 disappears from the interface. In this way, when the user opens the note application, the user can view the screen recording video corresponding to screen recording video thumbnail 402 in the relevant interface of the note application.

[0129] It should be pointed out that the screen recording video thumbnail 402 disappears in the interface, which can be understood as the mobile phone canceling the display of the screen recording video thumbnail 402.

[0130] In one implementation, when the target application is opened and displays its application interface (e.g., an editable interface), it can respond to the drag-and-drop data transfer operation. The following example uses a user dragging a screen recording video thumbnail to the editable interface of a note-taking application to add the screen recording video corresponding to the screen recording video thumbnail to a note.

[0131] As shown in (1) in FIG4c, after the screen recording is completed, the screen recording video thumbnail 411 is displayed in the mobile phone interface. Continuing to refer to (1) in FIG4c, while the screen recording video thumbnail 411 is displayed, the mobile phone interface is the editable interface of the note application. Among them, the user can open the editable interface of the note application before the screen recording is completed, or after the screen recording is completed and before the screen recording video thumbnail 411 disappears. This embodiment does not limit this. Continuing to refer to (1) in FIG4c, the user long presses the screen recording video thumbnail 411. In response to the user operation, the screen recording video thumbnail 412 floats up, and the floating screen recording video thumbnail 412 can be dragged by the user. In order to distinguish it from the non-floating screen recording video thumbnail 411 originally displayed in the mobile phone interface, the screen recording video thumbnail that floats up and can be dragged by the user is referred to as the screen recording video thumbnail 412 in this embodiment, as shown in (2) in FIG4c. Continuing to refer to (2) and (3) in Figure 4c, the user can drag the screen recording video thumbnail 412 arbitrarily in the mobile phone display interface 413 (that is, the editable interface of the note application). For example, the user can drag the screen recording video thumbnail 412 to the editable area of ​​the editable interface of the note application and then let go. In response to the user operation, the screen recording video thumbnail 412 disappears from the interface (or cancels the display), and the mobile phone transfers the screen recording video corresponding to the screen recording video thumbnail 412 to the note application. The note application receives the screen recording video 414 corresponding to the screen recording video thumbnail 412 and adds the screen recording video 414 to the editable interface 415 of the note application, as shown in (4) in Figure 4c. At this point, the screen recording video corresponding to the screen recording video thumbnail 412 completes data transfer. That is, the user transfers the corresponding screen recording video to the note application by dragging the screen recording video thumbnail 412. Continuing to refer to (4) in Figure 4c, if the user clicks the switch control 416 of the screen recording video 414, then in response to the user operation, the note application can call the relevant video player to play the screen recording video 414.

[0132] In one implementation, the target application resides on the desktop and is triggered to start through relevant operations (such as drag operations), assuming the function of a data transfer transfer station, and the target application can also respond to data drag and drop operations. The following example takes the case where a user drags a screen recording video thumbnail to a designated application, and the screen recording video corresponding to the screen recording video thumbnail is transferred to a video sharing application through the designated application. Among them, the designated application can be understood as a transfer station for data transfer, which can transfer the data it receives to the application or application service that has been registered in the designated application. It can be understood that the application or application service displayed in the designated application interface is the application or application service that has been registered in the designated application.

[0133] As shown in (1) in Figure 4d, after the screen recording is completed, the screen recording video thumbnail 421 is displayed in the mobile phone interface. The user long presses the screen recording video thumbnail 421. In response to the user operation, the screen recording video thumbnail 422 floats up, and the floating screen recording video thumbnail 422 can be dragged by the user. In order to distinguish it from the non-floating screen recording video thumbnail 421 originally displayed in the mobile phone interface, the screen recording video thumbnail that floats up and can be dragged by the user is called the screen recording video thumbnail 422 in this embodiment, as shown in (2) in Figure 4d. The user can drag the screen recording video thumbnail 422 arbitrarily in the mobile phone display interface. For example, the user drags resource data (such as image data, video data, file data, text data, etc.) to a hot zone at a preset position on the mobile phone desktop (for example, a hot zone set in the right edge area of ​​the desktop, or a hot zone set in the left edge area of ​​the desktop), which can trigger the opening of a specified application. For example, as shown in (3) in FIG4d, the user drags the screen recording video thumbnail 422 to the hot zone on the right edge of the mobile phone desktop. In response to the user operation, the designated application is opened, and the mobile phone displays the interface of the designated application, which can be referred to as the interface shown in (4) in FIG4d. At this time, the user can drag the screen recording video thumbnail 422 to any business icon displayed in the designated application interface. Among them, the business icon can be the same as the application icon of the application to which the business belongs, or it can be different from the application icon of the application to which the business belongs, and this embodiment does not limit this. If a video sharing application registers its multiple services in the designated application, the business icon corresponding to each business can be displayed separately in the interface of the designated application. For example, if the "Share with Friends" service and the "Publish to XX Platform" service of a video sharing application are both registered in the designated application, the business icon 1 corresponding to the "Share with Friends" service and the business icon 2 corresponding to the "Publish to XX Platform" service are displayed in the interface of the designated application. Among them, the icon images of business icon 1 and business icon 2 can be the same or different, and this embodiment does not limit this.

[0134] Continuing with reference to (1) in FIG4e , the user drags the screen recording video thumbnail 422 to the designated application interface. For a better visual experience, the size of the screen recording video thumbnail 422 can be reduced so that the screen recording video thumbnail can be fully displayed in the interface of the designated application, as shown in the screen recording video thumbnail 423. Continuing with reference to (2) in FIG4e , the user drags the screen recording video thumbnail 423 to the service icon corresponding to the "Share with Friends" service of a certain video sharing application. That is, the screen recording video thumbnail 423 is dragged by the user to the hot zone of the "Share with Friends" service icon. Exemplarily, in response to the user operation, the "Share with Friends" service icon becomes larger to prompt the user that the application service for receiving video data has been selected. After the user drags the screen recording video thumbnail 423 to the "Share with Friends" service icon in the designated application interface, the user releases the screen recording video thumbnail. In response to the user's hand-off operation, the screen recording video thumbnail 423 disappears in the interface (or is canceled), and the mobile phone sends the screen recording video corresponding to the screen recording video thumbnail 423 to the designated application. The designated application receives the screen recording video corresponding to the screen recording video thumbnail 423 and passes the screen recording video to the "Share with Friends" service in a certain video sharing application. At this point, the screen recording video corresponding to the screen recording video thumbnail 423 completes data transmission. That is, the user passes the corresponding screen recording video to the "Share with Friends" service in a certain video sharing application by dragging the screen recording video thumbnail 423. Exemplarily, after the user lets go, the mobile phone interface can jump to the "Share with Friends" service interface in the video sharing application, as shown in (3) in Figure 4e. Continuing to refer to (3) in Figure 4e, in the "Share with Friends" service interface in the video sharing application, a screen recording video corresponding to the screen recording video thumbnail 423 is displayed. The user can play the screen recording video in this interface, or share the screen recording video with one or more selected friends.

[0135] For example, when the user drags the screen recording video thumbnail 423 to another service icon in the specified application (such as the global favorites application icon) and releases the screen recording video thumbnail 423, the screen recording video thumbnail 423 disappears from the interface (or is canceled), and the mobile phone may also pop up a prompt message such as "Favorite Successful" or "Transfer Successful" to inform the user that the video data transfer is complete and exit the interface of the specified application. That is, when the user completes the screen recording video thumbnail dragging operation and releases the screen recording video thumbnail, the changes in the mobile phone interface are related to the recipient of the screen recording video data, which is not limited in this embodiment.

[0136] To summarize, when a user drags a screen recording video thumbnail or a screenshot image thumbnail, if there is a target application that can respond to the data drag and drop operation, the user can release the hand at the relevant interface of the target application, and the screen recording video thumbnail or the screenshot image thumbnail will disappear in the interface, thereby realizing the transfer of the video data or image data corresponding to the thumbnail to the target application.

[0137] It should be noted that, when the screen recording video thumbnail or the screenshot image thumbnail is dragged, no thumbnail is displayed at the position where the screen recording video thumbnail or the screenshot image thumbnail is initially displayed in the mobile phone display interface. Taking the scene shown in Figures 4d-4e as an example, when the screen recording video thumbnail 422 is dragged, as shown in (3) in Figure 4d, there is no thumbnail displayed at the position area 423 where the screen recording video thumbnail 421 (or screen recording video thumbnail 422) is initially displayed. The same is true for the screen recording video thumbnail dragging scene shown in Figures 4a-4b and the screen recording video thumbnail dragging scene shown in Figure 4c, which will not be repeated here.

[0138] It should be noted that when the user starts dragging the screen recording video thumbnail or the screenshot image thumbnail, the screen recording application cancels the automatic disappearance timer for the dragged screen recording video thumbnail, or the screenshot application cancels the automatic disappearance timer for the screenshot image thumbnail, to avoid the screen recording video thumbnail or the screenshot image thumbnail being destroyed during the dragging process.

[0139] It should also be pointed out that when the user drags a screen recording video thumbnail or a screenshot image thumbnail, if the target application can respond to the data drag and drop operation, but due to issues such as permissions, the data drag and drop operation cannot be normally affected at present, then when the user lets go of the relevant interface of the target application, in response to the user's hand-off operation, the mobile phone can pop up a relevant prompt box to guide the user to solve the permission problem and other issues, and continue to execute the operation of transferring the resource data corresponding to the thumbnail after the permission problem and other issues are resolved. If the permission problem is not resolved or the user refuses to resolve it, it indicates that the resource data corresponding to the thumbnail cannot be successfully transferred. At this time, the mobile phone will reset the display of the corresponding thumbnail. For relevant explanations on the reset display of the thumbnail, please refer to the following.

[0140] When a user drags a screen recording video thumbnail or screenshot image thumbnail, if the target application cannot respond to the data drag and drop operation, then when the user releases the target application's related interface, the screen recording video thumbnail will be reset in response to the user's release operation. If the target application can respond to the data drag and drop operation, if the user releases the target application in a non-hot area, the screen recording video thumbnail will also be reset in response to the user's release operation. In other words, if the user drags the screen recording video thumbnail to any non-hot area and releases the screen recording video thumbnail, the screen recording video thumbnail will be reset in response to the user's release operation.

[0141] Figure 4f exemplarily shows a schematic diagram of a scenario in which a screen recording video thumbnail is dragged and reset to display. As shown in (1) in Figure 4f, after the screen recording is completed, a screen recording video thumbnail 431 is displayed in the lower left corner of the mobile phone interface. The user long presses the screen recording video thumbnail 431. In response to the user operation, the screen recording video thumbnail floats up, and the floating screen recording video thumbnail can be dragged by the user. In order to distinguish it from the non-floating screen recording video thumbnail 431 originally displayed in the mobile phone interface, in this embodiment, the screen recording video thumbnail that floats up and can be dragged by the user is called screen recording video thumbnail 432, as shown in (2) in Figure 4f. Continuing to refer to (3) in Figure 4f, the user drags the screen recording video thumbnail 432 to the music application icon and lets go. Since the music application cannot respond to the data drag and drop operation, the screen recording application responds to the user's hand-off operation and restores the screen recording video thumbnail to display. When the screen recording video thumbnail is restored, the screen recording video thumbnail 432 that is floating and supports dragging is moved back to the initial position and disappears, and the screen recording video thumbnail 431 that is not floating and cannot be directly dragged is redisplayed, as shown in (4) in Figure 4f. It can be understood that the screen recording video thumbnail shown in (4) in Figure 4f is the same as the screen recording video thumbnail shown in (1) in Figure 4f.

[0142] It should be noted that after the screen recording video thumbnail or screenshot image thumbnail is reset and displayed, the screen recording application will restart the automatic disappearance timer for the screen recording video thumbnail, or the screenshot application will restart the automatic disappearance timer for the screenshot image thumbnail.

[0143] As an optional implementation, after the user starts dragging the screen recording video thumbnail or the screenshot image thumbnail, the mobile phone displays a frame (or wireframe, etc.) at the original display position of the thumbnail. The frame can be used to indicate the starting dragging area of ​​the thumbnail image, and can visually prompt the user to stop dragging the thumbnail within the frame area and release the hand to cancel the thumbnail dragging operation. The shape of the frame can be the same as the shape of the thumbnail, or different from the shape of the thumbnail, and this embodiment does not limit this. The size of the frame can be the same as the size of the thumbnail, or different from the size of the thumbnail (for example, the size of the frame is smaller than the size of the thumbnail), and this embodiment does not limit this.

[0144] If the user drags the screen recording video thumbnail (or screenshot image thumbnail) into the frame area and releases the hand to cancel the thumbnail dragging operation, the screen recording application (or screenshot application) will respond to the user operation and reset the screen recording video thumbnail (or screenshot image thumbnail). After the screen recording video thumbnail (or screenshot image thumbnail) is reset, the screen recording application (or screenshot application) restarts the automatic disappearance timer for the screen recording video thumbnail (or screenshot image thumbnail). Before the automatic disappearance timer ends (that is, before the thumbnail disappears), the user can also trigger the draggable function of the thumbnail again by long pressing.

[0145] As shown in (1) in Figure 4g, after the screen recording is completed, a screen recording video thumbnail 441 is displayed in the lower left corner of the mobile phone interface. The user long presses the screen recording video thumbnail 441. In response to the user operation, the screen recording video thumbnail floats up, and the floating screen recording video thumbnail can be dragged by the user. In order to distinguish it from the non-floating screen recording video thumbnail 441 originally displayed in the mobile phone interface, in this embodiment, the screen recording video thumbnail that floats up and can be dragged by the user is called a screen recording video thumbnail 442, as shown in (2) in Figure 4g. Continuing to refer to (3) in Figure 4g, the user starts to drag the screen recording video thumbnail 442. In response to the user's dragging operation, the mobile phone displays a frame 443 at the original position of the screen recording video thumbnail 442. Among them, the shape of the frame 443 can be the same as the shape of the screen recording video thumbnail 442, both of which are rectangular. The shape of the frame 443 can also be the same as the shape of the screen recording video thumbnail 442, for example, the shape of the frame 443 is square, circular, etc., and this embodiment does not limit this. The size of the frame 443 can be the same as the size of the screen recording video thumbnail 442, or it can be different from the size of the screen recording video thumbnail 442 (for example, the size of the frame 443 is slightly smaller than the size of the screen recording video thumbnail 442), and this embodiment does not limit this. Among them, the frame 443 can be used to prompt the user to stop dragging the thumbnail in the frame area and release the hand to cancel the thumbnail dragging operation. Continuing to refer to (4) in Figure 4g, the user continues to drag the screen recording video thumbnail 442 away from the original position. If the screen recording video thumbnail 442 and the frame 443 no longer have an intersection, the mobile phone cancels the display of the frame 443. Continuing with reference to FIG4h, the user drags the screen recording video thumbnail 442 toward the original position of the screen recording video thumbnail 442. If the screen recording video thumbnail 442 and the frame 443 intersect, the mobile phone redisplays the frame 443, thereby prompting the user to stop dragging the screen recording video thumbnail 442 within the frame 443 area and release the hand to cancel the thumbnail dragging operation. If the user stops dragging the screen recording video thumbnail 442 within the frame 443 area and releases the hand, in response to the user's operation, the mobile phone resets the display of the screen recording video thumbnail 442, as shown in FIG4g (1).

[0146] In order to enable the electronic device to implement the above-mentioned data transmission function based on long pressing and dragging of thumbnails, Figure 5 exemplarily shows a schematic diagram of the module interaction process of the electronic device. As shown in Figure 5, the data transmission method provided in the embodiment of the present application may include the following steps:

[0147] S501, in response to the user's screenshot operation or the operation of ending screen recording, the management module in the screenshot application (or screen recording application) generates a thumbnail view object corresponding to the screenshot image (or screen recording video) and starts the automatic disappearance timer for the thumbnail view object.

[0148] Exemplarily, the screenshot operation may refer to the operation of double-clicking the screen with a finger, clicking a shortcut switch, pressing a combination key, etc. In response to the user's screenshot operation, the screenshot application stores the screenshot image in the gallery application and generates a thumbnail view object corresponding to the screenshot image. The thumbnail view object is displayed on the current display interface of the electronic device, for example, at the lower left corner of the current display interface of the electronic device, as shown in (2) in Figure 3b.

[0149] Exemplarily, the operation of ending screen recording can be an operation of clicking the screen recording prompt control (as shown in (1) in Figure 3a), or an operation of clicking a shortcut switch, pressing a combination button, etc. In response to the user's execution of the operation of ending screen recording, the screen recording application stores the screen recording video in the gallery application and generates a thumbnail view object corresponding to the screen recording video. The thumbnail view object is displayed on the current display interface of the electronic device, for example, at the lower left corner of the current display interface of the electronic device, as shown in (2) in Figure 3a.

[0150] In the following process, the thumbnail view object can refer to a screenshot image thumbnail view object or a screen recording video thumbnail view object. After any type of thumbnail view object is displayed on the current display interface of the electronic device, the management module of the corresponding application starts an automatic disappearance timer for the thumbnail view object. Before the end of the automatic disappearance timer, if the user does not perform any operation on the thumbnail view object, the management module destroys the thumbnail view object, and the thumbnail view object automatically disappears from the electronic device display interface, as shown in (3) in Figure 3a or (3) in Figure 3b.

[0151] S502: The management module constructs a long press listener object and binds the long press listener object to the thumbnail view object.

[0152] After generating the thumbnail view object, the management module constructs a long click listener (OnLongClickListener) object for the thumbnail view object, and can bind the OnLongClickListener object to the thumbnail view object through the setOnLongClickListener(@Nullable OnLong ClickListener l) method.

[0153] S503 , in response to the user's long press operation on the thumbnail view object, the view system sends a long press event to the long press listener object and calls the long press drag method in the long press listener object.

[0154] When the user long presses the thumbnail view object (for example, as shown in (1) in Figure 4a), in response to the user operation, the view system sends a long press event to the OnLongClickListener object bound to the thumbnail view object, and calls the long press and drag (onLongClick(View v)) method in the OnLongClickListener object to execute the thumbnail start drag logic.

[0155] In this embodiment of the present application, the logic for initiating a thumbnail drag is defined in the onLongClick(View v) method of the OnLongClickListener object. Referring to Figure 6a , the logic for initiating a thumbnail drag is as follows: resetting the thumbnail view object, creating a draggable thumbnail image, initiating a thumbnail drag, and hiding the thumbnail view object. A detailed explanation of this logic can be found in steps S504-S509 below and will not be repeated here.

[0156] S504: Long press the listener object to reset the thumbnail view object.

[0157] Considering that the user may move the thumbnail view object while long pressing the thumbnail view object, such as swiping up or down (refer to the scenarios shown in Figures 3d and 3e), in order to be compatible with the swiping up sharing scenario for thumbnails and the swiping down to capture long images scenario, this embodiment needs to first reset the thumbnail view object before starting to drag the thumbnail, so that the position of the subsequently created draggable thumbnail image will not be offset.

[0158] Among them, long pressing the listener object to reset the thumbnail view object is to restore the thumbnail view object to its initial position. It can be understood that the initial position is the position where the thumbnail view object is initially displayed after the screen recording application or screenshot application generates the thumbnail view object.

[0159] Exemplarily, the long press listener object can call the updateViewLayout method provided by the window manager (WindowManager) to reset the layout of the thumbnail view object to restore the thumbnail view object to its initial position.

[0160] As an optional implementation, S504 may also be adjusted to: long-pressing the listener object to send an instruction message to the management module for instructing to reset the thumbnail view object, and the management module resets the thumbnail view object according to the instruction message. The management module may call the updateViewLayout method provided by the window manager (WindowManager) to reset the layout of the thumbnail view object, thereby restoring the thumbnail view object to its initial position.

[0161] S505 , the long press listener object creates a DragShadowBuilder object with the thumbnail image as a parameter.

[0162] Because thumbnail view objects don't support standard Android dragging, implementing the thumbnail dragging scenario described above requires creating thumbnail images that support standard Android dragging (referred to as draggable thumbnail images). To ensure the user's visual experience is consistent, draggable thumbnail images must use the image corresponding to the thumbnail view object as parameters, ensuring that the draggable thumbnail image and the thumbnail view object appear identical to each other.

[0163] In this embodiment, the long-press listener object creates a DragShadowBuilder object, defined by the view system, to generate a draggable thumbnail image. The DragShadowBuilder object is created with the thumbnail image as a parameter. The DragShadowBuilder object can be used to generate a DragShadow object, which is a standard draggable image in the Android system and can follow the user's finger.

[0164] In this embodiment, the DragShadow object generated by the DragShadowBuilder object is the draggable thumbnail image corresponding to the thumbnail view object. The DragShadow object can be understood as a projection of the thumbnail view object. The DragShadow object and the thumbnail view object have the same image screen and the same visual effect.

[0165] It's important to note that the initial display position of the draggable thumbnail image is the same as the position to which the thumbnail view object was restored. This means that the initial layout positions of the DragShadow object and the thumbnail view object are the same. Therefore, the user visually perceives dragging the original thumbnail (i.e., the thumbnail view object).

[0166] S506 , long-press the listener object to create a data structure object that supports dragging and dropping, and fill in the URI (Uniform Resource Identifier) ​​of the resource corresponding to the thumbnail view object.

[0167] The data structure object is used to store data to be transmitted. In an embodiment of the present application, the data structure object is used to store the URI of the resource corresponding to the thumbnail view object. When the thumbnail view object is a screenshot image thumbnail view object, the resource corresponding to the thumbnail view object is the screenshot image; when the thumbnail view object is a screen recording video thumbnail view object, the resource corresponding to the thumbnail view object is the screen recording video.

[0168] Exemplarily, the data structure object may be a ClipData object.

[0169] S507 : Long press the listener object to call the startDragAndDrop method to start dragging the draggable thumbnail image.

[0170] In an embodiment of the present application, a dragging method that carries data is used for dragging a draggable thumbnail image. The data carried by the draggable image can be transferred across processes. In an embodiment of the present application, this specifically refers to the fact that the resources carried by the draggable thumbnail image (i.e., screenshot image data or screen recording video data) can be transferred across processes.

[0171] For example, by long pressing the listener object, the startDragAndDrop method provided by the view system can be called to start dragging the draggable thumbnail image, wherein the calling parameters of the startDragAndDrop method are a DragShadowBuilder object and a ClipData object.

[0172] At this point, the screenshot / screen recording application has completed the preparations for the thumbnail image dragging function, and the subsequent implementation of the thumbnail image dragging function is completed by the view system.

[0173] S508 , the view system executes the startDragAndDrop method to start the drag function for the draggable thumbnail image, and returns the call result to the long press listener object.

[0174] When the long-press listener object is called, the view system executes the startDragAndDrop method to initiate the data-carrying dragging functionality for the draggable thumbnail image. During the execution of the startDragAndDrop method, the view system uses the DragShadowBuilder object to generate a DragShadow object, thereby generating the draggable thumbnail image. After the view system executes the startDragAndDrop method, the user can drag the draggable thumbnail image and transfer resource data through dragging, as shown in Figures 4a and 4b.

[0175] Exemplarily, the call result may be used to indicate whether the startDragAndDrop method is executed successfully, or whether the startDragAndDrop method is called successfully.

[0176] After the view system executes the startDragAndDrop method, the hand-following effect of the draggable thumbnail image is displayed, that is, the thumbnail image floats up as described above. It can be understood that the screen recording video thumbnail 402 shown in Figures 4a and 4b is the draggable thumbnail image mentioned in this process, and the screen recording video thumbnail 401 is the thumbnail view object mentioned in this process. Similarly, the screen recording video thumbnail 412 shown in Figure 4c is the draggable thumbnail image mentioned in this process, and the screen recording video thumbnail 411 is the thumbnail view object mentioned in this process. The same is true for other figures, which will not be repeated here.

[0177] S509: Long press the listener object to hide the thumbnail view object.

[0178] In the embodiment of the application, when the user drags the thumbnail image, the thumbnail image is no longer displayed at the initial position where the thumbnail image is displayed. Therefore, after creating the draggable thumbnail image, long pressing the listener object can hide the thumbnail view object, and the thumbnail view object will no longer be displayed while the draggable thumbnail image is being dragged by the user.

[0179] Optionally, the long press listener object can hide the thumbnail view object by setting the transparency. For example, the long press listener object can set the transparency of the thumbnail view object to 0 through the setAlpha(0) function, that is, the thumbnail view object is set to a fully transparent state.

[0180] Optionally, the long press listener object can hide the thumbnail view object by setting its visibility. For example, the long press listener object can set the visibility of the thumbnail view object to invisible by calling the setVisibility(View.GONE) function.

[0181] Optionally, the long press listener object can hide the thumbnail view object by adjusting its size. For example, the long press listener object can call the updateViewLayout method provided by the Window Manager to set the length and width of the thumbnail view object to 0, making the thumbnail view object invisible. Before the long press listener object adjusts the size of the thumbnail view object, the original dimensions of the thumbnail view object need to be recorded so that the size of the thumbnail view object can be restored later.

[0182] As an optional implementation, S509 may also be adjusted to: long-pressing the listener object to send an instruction message to the management module for instructing to hide the thumbnail view object, and the management module hides the thumbnail view object according to the instruction message. The management module may hide the thumbnail view object by setting its transparency, visibility, or size.

[0183] This embodiment does not limit the timing sequence of S508 and S509.

[0184] It's important to note that because the draggable thumbnail image is a DragShadow object corresponding to the thumbnail view object, the initial display position of the draggable thumbnail image is the same as the initial position of the thumbnail view object after it is reset. After the thumbnail view object is hidden, if the draggable thumbnail image is moved or dragged by the user, no thumbnail image will be displayed at the initial display position.

[0185] As an optional implementation, after the viewing system generates and displays the draggable thumbnail image, the viewing system may adjust the display position of the draggable thumbnail image based on the user's pressed position so that the user's pressed position is located in the center area of ​​the draggable thumbnail image. For example, the display position of the draggable thumbnail image may be adjusted so that the user's pressed position is the center point of the draggable thumbnail image.

[0186] As shown in Figure 6b (1), after the screen recording is completed, the screen recording video thumbnail 601 (i.e., the thumbnail view object) is displayed in the mobile phone interface. The user long presses the screen recording video thumbnail 601. In response to the user operation, the view system generates a draggable screen recording video thumbnail 602 at the same position as the screen recording video thumbnail 601, and the screen recording video thumbnail 602 floats up to prompt the user to drag the screen recording video thumbnail 602. Continuing to refer to (2) in Figure 6b, since the user's pressing position is not located in the center area of ​​the screen recording video thumbnail 602, the user's visual experience of dragging the screen recording video thumbnail 602 is not good. At this time, the view system can automatically adjust the display position of the screen recording video thumbnail 602 according to the user's pressing position, so that the user's pressing position can be located in the center area of ​​the screen recording video thumbnail 602, as shown in (3) in Figure 6b. Among them, the position adjustment process of the screen recording video thumbnail 602 shown in (2) to (3) in Figure 6b can be displayed in the form of a position movement animation to avoid the position of the screen recording video thumbnail 602 being moved instantly and affecting the user's visual experience. It should be pointed out that, as shown in (3) in Figure 6b, since the screen recording video thumbnail 601 has been hidden, there is no thumbnail image displayed at the initial display position of the screen recording video thumbnail 602. At the same time, since the screen recording video thumbnail 602 and the frame 603 have an intersection, the frame 603 is shown in an opaque form.

[0187] Comparing (2) in FIG6b and (3) in FIG6b, it can be seen that compared with the user dragging the screen recording video thumbnail 602 at the edge thereof, the user's operation experience of dragging the screen recording video thumbnail 602 at the center area thereof is better.

[0188] S510: Long press the listener object to send thumbnail dragging permission indication information to the management module.

[0189] The thumbnail dragging permission indication information may be used to indicate that the dragging function of the draggable thumbnail image has been started, and the user may perform a dragging operation on the draggable thumbnail image.

[0190] S511, the management module generates a frame view object.

[0191] After the dragging function of the draggable thumbnail image is started, the management module creates a frame view object corresponding to the thumbnail image at the initial position of the thumbnail view object. The frame view object can be shown as frame 443 in (3) of Figure 4g.

[0192] The shape of the frame view object can be the same as or different from the thumbnail shape, and this embodiment does not limit this. The size of the frame view object can be the same as or different from the thumbnail size (for example, the frame size is smaller than the thumbnail size), and this embodiment does not limit this.

[0193] In this embodiment, the frame view object can be used to visually prompt the user, prompting the user to stop dragging the thumbnail in the frame area and release the thumbnail to cancel the thumbnail dragging operation.

[0194] Optionally, the management module may also pre-generate a frame view object when generating a thumbnail view object. This embodiment does not limit the timing of generating the frame view object.

[0195] As an optional implementation, the size of the frame view object is always the same as that of the thumbnail view object. When the management module hides the thumbnail view object by adjusting the size of the thumbnail view object, the management module also adjusts the size of the frame view object accordingly to hide the frame view object.

[0196] In this way, if the startup hot zone of the designated application as shown in FIG. 4 d and FIG. 4 e is set in the left edge area of ​​the desktop, hiding the frame view object will not affect the startup of the designated application.

[0197] S512: The management module constructs a drag-and-drop listener object, and binds the drag-and-drop listener object to the frame view object.

[0198] The drag-and-drop listener (OnDragListener) object, which may also be called a drag (or drag) listener object, is used to monitor the user's dragging action (or dragging action) on the draggable thumbnail image.

[0199] In this embodiment, the management module constructs an OnDragListener object and can bind the OnDragListener object to the frame view object through the setOnDragListener(OnDragListener 1) method. In this way, the frame view object can not only serve as a visual cue but also perceive the drag event at a technical level.

[0200] Optionally, the OnDragListener object constructed by the management module may also be bound to other view objects, which is not limited in this embodiment.

[0201] S513 , in response to the user's dragging operation on the draggable thumbnail image, the view system distributes the drag event to the drag and drop listener object and calls the action response method in the drag and drop listener object.

[0202] When the user drags the draggable thumbnail image (for example, refer to (3) and (4) in Figure 4a, and (1) and (2) in Figure 4b), in response to the user operation, the view system distributes the drag event to the OnDragListener object and calls the action response (onDrag(View, DragEvent)) method in the OnDragListener object to respond to the user's drag / drop operation.

[0203] In an embodiment of the present application, the processing logic for responding to a user dragging a draggable thumbnail image is defined in the (onDrag(View, DragEvent)) method in the OnDragListener object. Referring to Figure 6c, the processing logic for responding to a user dragging / dropping a draggable thumbnail image is as follows: obtaining the operation type of the user operation, and responding to the user operation according to the operation type. Among them, when the operation type indicates that the drag action has started, the automatic disappearance timing for the thumbnail view object is canceled; when the operation type indicates that the user has released the hand and the drag action has ended, it is continued to determine whether the resource data carried by the draggable thumbnail image has been processed. If the resource data has been processed, the thumbnail view object is destroyed; otherwise, the thumbnail view object is unhidden and the automatic disappearance timing of the thumbnail view object is restarted.

[0204] When the management module does not adjust the size of the frame view object, when the operation type indicates that the draggable thumbnail image intersects with the frame view object, that is, when the thumbnail image is dragged into the area corresponding to the frame view object, the frame view object is set to opaque; when the operation type indicates that the draggable thumbnail image leaves the area corresponding to the frame view object and has no intersection with the frame view object, the frame view object is set to transparent.

[0205] For a detailed explanation of these processing logics, please refer to the following related steps S515-S523, which will not be repeated here.

[0206] The embodiment of the present application does not limit the timing sequence of S513 and S514 - S520 .

[0207] S514 , in response to the user's dragging operation on the draggable thumbnail image, the view system implements a drag / drop function carrying resource data for the draggable thumbnail image.

[0208] Among them, when the user drags the draggable thumbnail image, the view system can implement the dragging function of carrying resource data for the draggable thumbnail image, that is, realize the technical effect of image draggability and data transferability.

[0209] When the user drags the draggable thumbnail image without releasing it, the view system implements the effect that the draggable thumbnail image follows the movement of the user's finger based on the Android system drag and drop framework. When the user releases the hand to end the drag operation, the view system determines whether the resource data carried by the draggable thumbnail image can be processed, that is, whether it can be passed to the target application based on the Android system drag and drop framework. If the target application where the user releases the hand can respond to the drag data transmission, the view system passes the resource data carried by the draggable thumbnail image to the target application based on the Android system drag and drop framework. At this time, the resource data carried by the draggable thumbnail image is processed, otherwise the resource data carried by the draggable thumbnail image is not processed.

[0210] Among them, the Android system drag and drop framework is a native technology of the Android system. Applications can implement the drag and drop function of carrying resource data by calling and accessing the Android system drag and drop framework.

[0211] After passing the resource data carried by the draggable thumbnail image to the target application, the view system can destroy the draggable thumbnail image. When the user releases the drag operation to end the drag operation, if the resource data carried by the draggable thumbnail image has not been processed, the view system can destroy it after resetting the draggable thumbnail image (i.e., restoring the draggable thumbnail image to its initial position). Optionally, when the user releases the drag operation to end the drag operation, if the resource data carried by the draggable thumbnail image has not been processed, the view system can also directly destroy the draggable thumbnail image.

[0212] As you can understand, when the user releases their hand, indicating the end of the drag operation, the view system can destroy the DragShadowBuilder and ClipData objects. When the user long-presses the thumbnail view object again, the long-press listener object can recreate the DragShadowBuilder and ClipData objects based on the thumbnail view object and use them as call parameters to the startDragAndDrop method provided by the view system.

[0213] S515 , the drag-and-drop listener object obtains that the operation type of the drag event is drag start, and then executes S516 .

[0214] When the drag and drop listener object executes the action response method, it first obtains the operation type of the drag event, that is, obtains the user's operation type, and performs the corresponding operation based on the obtained operation type and the preset logic.

[0215] Illustratively, when the operation type is defined by the view system, the drag and drop listener object can use the dragEvent.getAction() method to obtain the operation type of the user operation.

[0216] For example, the operation type "DragEvent.ACTION_DRAG_STARTED" indicates that a drag action has started. When the drag listener object receives a drag event with the operation type "DragEvent.ACTION_DRAG_STARTED", it determines that the user has started dragging the draggable thumbnail image.

[0217] S516: The drag-and-drop listener object cancels the automatic disappearance timing of the thumbnail view object.

[0218] To prevent the thumbnail view object from automatically disappearing while the user is dragging the draggable thumbnail image, the automatic disappearance timer for the thumbnail view object is first canceled when the user starts dragging the draggable thumbnail image.

[0219] Among them, the drag and drop listener object can directly cancel the automatic disappearance timer for the thumbnail view object, or it can send an indication message to the management module to instruct the management module to cancel the automatic disappearance timer for the thumbnail view object. The management module will cancel the automatic disappearance timer for the thumbnail view object according to the indication message. This embodiment does not limit this.

[0220] S517 , the drag-and-drop listener object obtains that the operation type of the drag event is entering the frame or leaving the frame, and then executes S518 .

[0221] S518 , drag and drop the listener object to adjust the transparency of the frame view object.

[0222] Among them, the drag and drop listener object obtains the operation type of the drag event as entering the frame, that is, the dragged thumbnail image and the area corresponding to the frame view object intersect, and the drag and drop listener object sets the frame view object to non-transparent (such as opaque or semi-transparent). The drag and drop listener object obtains the operation type of the drag event as leaving the frame, that is, the dragged thumbnail image and the area corresponding to the frame view object do not intersect, and the drag and drop listener object sets the frame view object to fully transparent.

[0223] For example, the operation type "DragEvent.ACTION_DRAG_ENTERED" indicates that the thumbnail image can be dragged into the area corresponding to the frame view object and has an intersection with the frame view object. The operation type "DragEvent.ACTION_DRAG_EXITED" indicates that the thumbnail image can be dragged out of the frame view object and has no intersection with the frame view object.

[0224] When the drag-and-drop listener object receives a drag event with the action type "DragEvent.ACTION_DRAG_ENTERED," the drag-and-drop listener object sets the frame view object to a non-transparent state (e.g., opaque or semi-transparent) to display the frame view object, as shown in (3) in FIG4g . For example, the drag-and-drop listener object can set the frame view object to an opaque state using the function setAlpha(1), thereby displaying the frame view object and prompting the user.

[0225] When the drag and drop listener object receives a drag event with the action type "DragEvent.ACTION_DRAG_EXITED", the drag and drop listener object sets the frame view object to be fully transparent, as shown in (4) in Figure 4h. For example, the drag and drop listener object can set the frame view object to be fully transparent using the function setAlpha(0), thereby achieving the effect of hiding the frame view object.

[0226] As an optional implementation, S518 can also be adjusted as follows: the drag and drop listener object sends an indication message to the management module for instructing to adjust the transparency of the frame view object, and the management module adjusts the transparency of the frame view object according to the indication message. When the drag and drop listener object receives a drag event with an operation type of "DragEvent.ACTION_DRAG_ENTERED", the drag and drop listener object sends an indication message to the management module for instructing to set the transparency of the frame view object to non-transparent, and the management module sets the frame view object to non-transparent according to the indication message. When the drag and drop listener object receives a drag event with an operation type of "DragEvent.ACTION_DRAG_EXITED", the drag and drop listener object sends an indication message to the management module for instructing to set the transparency of the frame view object to fully transparent, and the management module sets the frame view object to fully transparent according to the indication message.

[0227] It should be noted that if the size of the frame view object is adjusted, for example, the length and width of the frame view object are adjusted to 0, then S517 - S518 may not be executed.

[0228] S519: The drag-and-drop listener object obtains that the operation type of the drag event is a release operation, and executes S520.

[0229] For example, the operation type "DragEvent.ACTION_DRAG_ENDED" indicates that the user has released the drag operation. When the drag listener object receives a drag event with the operation type "DragEvent.ACTION_DRAG_ENDED", it determines that the user has ended the drag operation on the draggable thumbnail image.

[0230] S520 , the drag and drop listener object queries whether the resource data carried by the draggable thumbnail image has been processed, if so, execute S521 , if not, execute S522 .

[0231] Illustratively, the drag and drop listener object may use the dragEvent.getResult() method to query whether the resource data carried by the draggable thumbnail image has been processed.

[0232] The resource data carried by the draggable thumbnail image has been processed, which can be understood as the screenshot image or screen recording video corresponding to the thumbnail view object has been transmitted to the target application or service.

[0233] Situations where the resource data carried by the draggable thumbnail image is not processed may include the user dragging the draggable thumbnail image into a non-hot zone and then releasing the image, or the user dragging the draggable thumbnail image into the hot zone of the target application, but the target application is unable to respond to the data drag transfer operation.

[0234] S521, the drag and drop listener object destroys the thumbnail view object.

[0235] When the user releases the draggable thumbnail image and ends dragging it, if the drag and drop listener object finds that the data carried by the draggable thumbnail image has been processed, that is, the resource data has been passed to the target application, the drag and drop listener object destroys the thumbnail view object and the process ends.

[0236] As an optional implementation, S521 may be adjusted as follows: the drag-and-drop listener object sends instruction information for instructing the management module to destroy the thumbnail view object, and the management module destroys the thumbnail view object according to the instruction information.

[0237] S522 , drag and drop the listener object to unhide the thumbnail view object, and restart the automatic disappearance timer for the thumbnail view object.

[0238] When the user stops dragging the draggable thumbnail image, if the drag and drop listener object queries that the data carried by the draggable thumbnail image has not been processed, that is, the resource data has not been passed to the target application, the drag and drop listener object triggers the display of the thumbnail view object again and restarts the automatic disappearance timer for the thumbnail view object.

[0239] When the long press listener object hides the thumbnail view object by setting the transparency, the drag and drop listener object also unhides the thumbnail view object by setting the transparency. For example, the drag and drop listener object can set the transparency of the thumbnail view object to 1 through the setAlpha(1) function, which means that the thumbnail view object is set to an opaque state.

[0240] When the long press listener object hides the thumbnail view object by setting its visibility, the drag and drop listener object also unhides the thumbnail view object by setting its visibility. For example, the drag and drop listener object can set the visibility of the thumbnail view object to visible using the setVisibility(View.VISIBLE) function.

[0241] When the long press listener object hides the thumbnail view object by setting its size, the drag and drop listener object unhides the thumbnail view object by resizing it. For example, the drag and drop listener object can obtain the original size of the thumbnail view object recorded by the long press listener object and call the updateViewLayout method provided by the Window Manager to reset the size of the thumbnail view object to its original size.

[0242] As an optional implementation, S520 may be adjusted to include: dragging and dropping the listener object to send an instruction to the management module, the instruction information being used to instruct the management module to unhide the thumbnail view object and restart the automatic disappearance timer for the thumbnail view object. The management module, based on the instruction information, unhides the thumbnail view object and restarts the automatic disappearance timer for the thumbnail view object.

[0243] When a long press on a listener object hides a thumbnail view object by setting transparency, the management module also unhides the thumbnail view object by setting transparency. When a long press on a listener object hides a thumbnail view object by setting visibility, the management module also unhides the thumbnail view object by setting visibility. When a long press on a listener object hides a thumbnail view object by setting the thumbnail view object size, the management module also unhides the thumbnail view object by resetting the thumbnail view object size.

[0244] In this case, since the thumbnail view object has not been destroyed, before the automatic disappearance timer of the thumbnail view object ends, the user can also trigger the data transmission process provided by the embodiment of the present application through a long press operation again. See S503 to S522 above for details, which will not be repeated here.

[0245] In the solution provided in the embodiment of the present application, the user can transfer data of the screenshot image or screen recording video corresponding to the thumbnail image by dragging the screenshot image thumbnail image or the screen recording video thumbnail image, which is convenient to operate and improves the user experience.

[0246] In addition, this embodiment of the application also takes into account existing solutions for automatically disappearing thumbnails, restarting the automatic disappearance timer after the thumbnail drag is canceled. Moreover, this embodiment of the application achieves the visual effect of "the original thumbnail is being dragged" by hiding the thumbnail view object, which is significantly different from the visual experience of the user clearly perceiving that the drag projection is being dragged.

[0247] This embodiment further provides a computer storage medium, in which computer instructions are stored. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the data transmission method in the above-mentioned embodiment.

[0248] This embodiment further provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the above-mentioned related steps to implement the data transmission method in the above-mentioned embodiment.

[0249] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory to enable the chip to execute the data transmission method in the above-mentioned method embodiments.

[0250] Among them, the electronic device, computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

[0251] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0252] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0253] Units described as separate components may or may not be physically separate, and components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0254] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0255] Any content of each embodiment of this application, as well as any content of the same embodiment, can be freely combined. Any combination of the above content is within the scope of this application.

[0256] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0257] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

[0258] The steps of the method or algorithm described in conjunction with the disclosure of the embodiments of the present application can be implemented in a hardware manner, or can be implemented by a processor executing a software instruction. The software instruction can be composed of corresponding software modules, and the software module can be stored in a random access memory (Random Access Memory, RAM), a flash memory, a read-only memory (Read Only Memory, ROM), an erasable programmable read-only memory (Erasable Programmable ROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), a register, a hard disk, a mobile hard disk, a read-only compact disc (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC.

[0259] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0260] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A data transmission method, It is characterized in that include: In response to the first operation, displaying a first thumbnail corresponding to the screenshot image or the screen recording video at a first position; In response to a second operation on the first thumbnail, creating a second thumbnail at the first position and hiding the first thumbnail, wherein the second thumbnail has the same image screen as the first thumbnail and the second thumbnail is a draggable image; In response to the movement of the third operation, the second thumbnail moves with the hand, the third operation acts on the second thumbnail, and the third operation is a drag operation that is continuous with the second operation; In response to the third operation, the second thumbnail is dragged to the first area and then released, the screenshot image or screen recording video corresponding to the first thumbnail is transmitted to the first service, and the first thumbnail and the second thumbnail are not displayed, wherein the first area is a hot zone corresponding to the first service.

2. The method according to claim 1, It is characterized in that The first service is a service that allows receiving the screenshot image or screen recording video.

3. The method according to claim 1, It is characterized in that Also includes: In response to the third operation, the second thumbnail is dragged to the second area and then released, the second thumbnail is moved to the first position, the second thumbnail is not displayed, and the first thumbnail is redisplayed; The second area is an area corresponding to a second service, and the second service is a service that does not allow receiving the screenshot image or screen recording video; or, the second area is a non-hot zone.

4. The method according to claim 1, It is characterized in that When the second thumbnail is dragged to the first area and then released, the first thumbnail is not displayed, including: A first drag event on the second thumbnail is monitored, where the operation type of the first drag event is drag end; It is found that the screenshot image or screen recording video has been transmitted and processed, and the first thumbnail is not displayed.

5. The method according to claim 3, It is characterized in that Drag the second thumbnail to the second area and then release the thumbnail to display the first thumbnail, including: A second drag event on the second thumbnail is monitored, where the operation type of the second drag event is drag end; It is found that the screenshot image or screen recording video has not been transmitted and processed, and the first thumbnail is redisplayed.

6. The method according to claim 1, hiding the first thumbnail, include: Recording the original size of the first thumbnail, and resetting the size of the first thumbnail to 0; Alternatively, the first thumbnail is set to be fully transparent; Alternatively, the visibility of the first thumbnail is set to invisible.

7. The method according to claim 1, It is characterized in that Also includes: In response to the second operation, generating a target frame at the first position, the target frame being used to indicate a start dragging area of ​​the second thumbnail; In response to the third operation, the second thumbnail is dragged to a third area to hide the target frame; wherein when the second thumbnail is located in the third area, there is no intersection between the second thumbnail and the target frame; In response to the third operation, the second thumbnail is dragged to a fourth area, and the target frame is displayed; wherein, when the second thumbnail is located in the fourth area, the second thumbnail and the target frame have an intersection.

8. The method according to claim 7, It is characterized in that Also includes: In response to the third operation, the second thumbnail is dragged to the fourth area and then released, the second thumbnail is moved to the first position, the second thumbnail is not displayed, and the first thumbnail is redisplayed.

9. The method according to claim 8, It is characterized in that In response to the third operation, the second thumbnail is dragged to the fourth area and then released, and the first thumbnail is redisplayed, comprising: A third drag event on the second thumbnail is monitored, where the operation type of the third drag event is drag end; It is found that the screenshot image or screen recording video has not been transmitted and processed, and the first thumbnail is redisplayed.

10. The method according to claim 7, It is characterized in that In response to the third operation, dragging the second thumbnail to a third area and hiding the target frame includes: monitoring a fourth drag event on the second thumbnail, and setting the target frame to be fully transparent; wherein the operation type of the fourth drag event is leaving the frame area; Dragging the second thumbnail to the fourth area to display the target frame includes: A fifth drag event on the second thumbnail is monitored, and the target frame is set to be non-transparent; wherein the operation type of the fifth drag event is entering a frame area.

11. The method according to any one of claims 1 to 10, It is characterized in that After displaying a first thumbnail corresponding to the screenshot image or the screen recording video at the first position, the method further includes: Starting a target timing for the first thumbnail; wherein the target timing is used to trigger non-display of the first thumbnail when the timing duration reaches a preset duration; Upon detecting a sixth drag event on the second thumbnail, the target timing for the first thumbnail is canceled; The operation type of the sixth drag event is drag start.

12. The method according to claim 11, It is characterized in that After redisplaying the first thumbnail, the method further includes: restarting the target timing for the first thumbnail.

13. The method according to claim 1, It is characterized in that After creating the second thumbnail at the first position, the method further includes: moving the second thumbnail from the first position to a second position according to the position of the second operation; When the second thumbnail is located at the second position, the position of the second operation is located in the central area of ​​the second thumbnail.

14. An electronic device, It is characterized in that include: Memory and processor; The processor is coupled to the memory; The memory stores program instructions, and when the program instructions are executed by the processor, the electronic device executes the data transmission method according to any one of claims 1 to 13.

15. A computer-readable storage medium comprising a computer program, It is characterized in that When the computer program is executed on an electronic device, the electronic device executes the data transmission method according to any one of claims 1 to 13.

Images