WO2024104094A1

WO2024104094A1 - Screenshot sharing method and electronic device

Info

Publication number: WO2024104094A1
Application number: PCT/CN2023/127434
Authority: WO
Inventors: 冯策
Original assignee: 华为技术有限公司
Priority date: 2022-11-17
Filing date: 2023-10-28
Publication date: 2024-05-23
Also published as: CN118101641A

Abstract

The present application discloses a screenshot sharing method and an electronic device. The electronic device 100 can be provided with a host operating system, and a client operating system can be loaded on the host operating system. After detecting an operation of a user triggering display of a screenshot interface, the electronic device 100 can support, by means of the host operating system, the user to freely carry out an image capturing operation and an image editing operation, etc. in any area, thereby generating a screenshot image, and save information of the screenshot image to a clipboard of the host operating system; then, the host operating system shares the information of the screenshot image to a clipboard of the client operating system, for use by an application of the client operating system, thereby achieving the effect that the application of the client operating system can directly paste the screenshot image. For a social application of the client operating system, the effect of one-key cross-system screenshot sharing can be achieved, user operations are simplified, and the user experience is improved.

Description

Screenshot sharing method and electronic device

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 17, 2022, with application number 202211463744.8 and application name “Screenshot Sharing Method and Electronic Device”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of computer technology, and in particular to a screenshot sharing method and electronic device.

Background technique

With the development and maturity of virtualization technology, traditional personal computers (PC) and mobile devices (such as mobile phones) can achieve ecological integration through technologies such as simulators, so that users can run applications of mobile operating systems (OS) on the PC.

However, in the above-mentioned ecological integration scenario, if users want to share screenshots through the mobile operating system application, they usually need to use the screenshot function provided by the simulator to save the screenshot image to the "Gallery" application of the mobile operating system, and then select the screenshot image saved in the "Gallery" application. After the selection is completed, the sharing operation is triggered. The whole process is relatively complicated. Moreover, the screenshot function provided by the simulator is relatively simple. At present, the simulator cannot fully utilize the powerful screenshot function provided by the PC operating system, and the ecological integration experience is poor.

Summary of the invention

The embodiments of the present application provide a screenshot sharing method and an electronic device, which can achieve the effect of one-click cross-system screenshot sharing, simplify user operations, and improve user experience.

In a first aspect, an embodiment of the present application provides a screenshot sharing method, which is applied to an electronic device, on which a first operating system and a second operating system are running, the method comprising: in response to a user's screenshot operation, the first operating system generates and saves a screenshot image; the second operating system obtains the screenshot image and saves the screenshot image to a clipboard of the second operating system; the second operating system displays a floating window in a user interface, the floating window is generated based on the screenshot image, and the user interface is a user interface of an application in the second operating system; the second operating system detects a first operation of the user on the floating window on the user interface; in response to the first operation, the electronic device sends the screenshot image to other devices.

By implementing the method provided in the first aspect, after detecting that a user triggers a screenshot operation, the electronic device can generate a screenshot image and save the information of the screenshot image to the clipboard of the host operating system (also referred to as the first operating system). Afterwards, the host operating system can share the information of the screenshot image to the clipboard of the client operating system (also referred to as the second operating system) for use by the client operating system's application, thereby achieving the effect that the client operating system's application can directly paste the screenshot image. For social applications of the client operating system, a one-click cross-system screenshot sharing effect can also be achieved, thereby simplifying user operations and improving user experience.

In a possible implementation, before the second operating system acquires the screenshot image, the method further includes: the first operating system sends a first message to the second operating system, where the first message is used to instruct the second operating system to acquire the screenshot image.

In this way, when there is newly saved content in the clipboard of the first operating system, the first operating system can notify the second operating system to obtain the newly saved content, so that the second operating system can use the content.

In a possible implementation, the first message is sent via inter-process communication (IPC).

In a possible implementation manner, the second operating system obtains the screenshot image, including: the second operating system receives the screenshot image sent by the first operating system.

In this way, when there is newly saved content in the clipboard of the first operating system, the first operating system can directly send the content to the second operating system so that the second operating system can use the content.

In a possible implementation manner, the first operating system saves the screenshot image, including: the first operating system saves the screenshot image to a clipboard of the first operating system and to a shared folder.

In this way, when there is newly saved content in the clipboard of the first operating system, the first operating system can also save the content to the shared folder, so that the second operating system can obtain the content in the shared folder.

In a possible implementation, before the first operating system sends the first message to the second operating system, the method further includes: first The operating system detected that the most recent content saved in the clipboard is a picture.

In this way, when the first operating system detects that the latest content saved in its clipboard is a picture (such as a screenshot image), it can save the picture to the shared folder, and at the same time, it can also notify the second operating system to obtain the picture in the shared folder.

In a possible implementation manner, the second operating system obtains the screenshot image, including: the second operating system obtains the screenshot image from a shared folder.

In this way, the second operating system can obtain the screenshot image in the shared folder, and then save the screenshot image to its clipboard, so that subsequent applications of the second operating system can use the screenshot image.

In a possible implementation, before the second operating system displays the floating window in the user interface, the method further includes: the second operating system scans the path of the screenshot image in the shared folder, and inserts the screenshot image information into the media database based on the path.

In a possible implementation, the second operating system inserts the information of the screenshot image into the media database based on the path, including: when the second operating system determines that the screenshot image meets the preset rules based on the path, the screenshot image information is inserted into the media database; wherein the preset rules include any one or more of the following: the naming of the screenshot image includes specific keywords, the time interval between the time point recorded in the timestamp information of the screenshot image and the first time point is within the preset time interval, and the first time point is the time point when the second operating system scans the path of the screenshot image in the shared folder.

In this way, the second operating system can insert the information of the screenshot image into the media database when it determines that the screenshot image meets preset rules (such as preset screenshot rules), so that when a subsequent application detects that the information inserted in the media database has changed, it can automatically trigger the display of a floating window, thereby achieving the effect of one-click cross-system screenshot sharing.

In a possible implementation, after the second operating system inserts the description information of the screenshot image into the media database based on the path, the method further includes: the application program obtains the screenshot image from the clipboard of the second operating system.

In this way, the application can obtain the screenshot image from the clipboard of the second operating system, so as to automatically trigger the display of a floating window in a certain user interface of the application (such as a chat interface), thereby achieving a one-click cross-system screenshot sharing effect.

In a possible implementation, the screenshot operation includes one or more of the following: an operation of selecting a screenshot area, and an editing operation on the screenshot area.

In this way, the first operating system can support users to freely perform image capture operations of any area, image editing operations, etc., which is convenient and flexible and improves user experience.

In a possible implementation, an input box and a control for file sharing are displayed in the user interface.

In this way, the application can specifically share the screenshot image capability, thereby supporting users to share the screenshot image.

In a second aspect, an embodiment of the present application provides an electronic device, which includes one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, and the computer program code includes computer instructions, and when the one or more processors execute the computer instructions, the electronic device executes the method in any possible implementation of the first aspect above.

In a third aspect, an embodiment of the present application provides a computer storage medium, which stores a computer program, and the computer program includes program instructions. When the program instructions are executed on an electronic device, the electronic device executes a method in any possible implementation of the first aspect above.

In a fourth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the method in any possible implementation of the first aspect above.

BRIEF DESCRIPTION OF THE DRAWINGS

1A-1B are schematic diagrams of user interfaces involved in a process of taking a screenshot of an electronic device 100 through an application of a client operating system provided by an embodiment of the present application;

FIG1C is a schematic diagram of a screenshot image generated by the screenshot process shown in FIG1A-FIG1B according to an embodiment of the present application;

1D-1G are schematic diagrams of user interfaces involved in a process of sharing a screenshot through an application of a client operating system of an electronic device 100 provided in an embodiment of the present application;

2A-2B are schematic diagrams of a set of user interfaces involved in the screenshot process of the screenshot sharing method provided in an embodiment of the present application;

FIG2C is a schematic diagram of a screenshot image generated by the screenshot process shown in FIG2A-FIG2B according to an embodiment of the present application;

2D-2E are schematic diagrams of a set of user interfaces involved in the screenshot sharing process of the screenshot sharing method provided in an embodiment of the present application;

3A-3C are schematic diagrams of another set of user interfaces involved in the screenshot process of the screenshot sharing method provided in an embodiment of the present application;

FIG3D is a schematic diagram of a screenshot image generated by the screenshot process shown in FIG3A to FIG3C provided in an embodiment of the present application;

3E-3F are another set of user interface schematic diagrams involved in the screenshot sharing process of the screenshot sharing method provided in an embodiment of the present application;

FIG4 is a schematic diagram of a process of a screenshot sharing method provided in an embodiment of the present application;

FIG5 is a schematic diagram of a software structure of an electronic device 100 provided in an embodiment of the present application;

FIG6 is a schematic diagram of the software structure of another electronic device 100 provided in an embodiment of the present application;

7 is a schematic diagram of a possible collaboration mode between various modules when the electronic device 100 provided by the embodiment of the present application implements the screenshot sharing method provided by the embodiment of the present application when a host operating system is installed and a client operating system is loaded on the host operating system;

FIG8 is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of the present application.

Detailed ways

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, "/" means or, for example, A/B can mean A or B; "and/or" in the text is only a description of the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

It should be understood that the terms "first", "second", etc. in the specification, claims and drawings of the present application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

Reference to "embodiments" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments.

The term "user interface (UI)" in the following embodiments of the present application refers to a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is a source code written in a specific computer language such as Java and extensible markup language (XML). The interface source code is parsed and rendered on an electronic device and finally presented as content that can be recognized by the user. The commonly used form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operation displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the display screen of an electronic device.

The mainstream computer desktop operating systems on the market include Mainstream mobile operating systems include Since the operating mechanisms of applications on different operating systems are different, there are barriers to communication and interaction between different operating systems, and in many aspects, it is difficult to achieve simple and effective ecological integration. Therefore, in general, applications on operating system A cannot be installed and run on operating system B. For example, Applications in the operating system cannot be directly installed and run on On the operating system.

With the development and maturity of virtualization technology, if users need to run or If the system application is virtualized, users can use virtualization technology to implement it, for example, using an Android emulator ( simulator), Android container ( container) and other technologies. For example, if you want to install an Android emulator on the operating system, you can first start Android emulator in the operating system, run subsystem, and then from Start the application in the subsystem.

In the above case, the computer can be called a host machine, and the underlying operating system running on the computer can be called a host operating system (Host OS). The operating system running in the simulator or container on the host can be called a guest operating system (Guest OS). At this time, the guest operating system can run on the host machine, and the host machine virtualizes a virtual hardware environment (including processor, memory, I/O devices, etc.) independent of the actual hardware for the simulator or container, so that for the guest operating system, running in the virtual hardware environment on the host machine is no different from running on the actual hardware. In this way, the ecology of computers and mobile devices can be integrated. As a fusion product, it can not only allow users to experience the rich applications provided by the mobile ecology, but also experience the interaction scenarios between the applications in the two ecology of computers and mobile devices. In the above ecological fusion scenario, users can use the applications of mobile devices just like using computer applications, and based on the high performance and display input devices of the computer, users can get a better experience than mobile devices in some aspects.

Screenshot operation is a high-frequency operation on mobile devices. Users can capture full-screen images through shortcut keys, gestures, clicking the screenshot option in the drop-down menu, etc. After the capture is completed, it can be saved as a picture in the "Gallery" application (also known as the "Album" application) of the operating system. Users can perform simple editing operations on the picture in the "Gallery" application (such as cropping the picture size, adjusting the picture color, mosaic, graffiti, etc.), and it can also support users to use and share the picture in other applications (such as social applications).

Currently, mainstream simulators basically provide the option to take screenshots of the entire user interface of an application to achieve the same experience as using a mobile device.

1A-1G , a set of user interfaces involved in the process of taking screenshots and sharing screenshots by an electronic device 100 through an application of a client operating system (eg, an operating system running in a simulator) are exemplarily introduced below.

In the embodiment of the present application, the electronic device 100 is taken as an example to be described as a notebook computer.

The user operations involved in the embodiments of the present application may be operations performed by the user through the keyboard or mouse of the electronic device 100, or operations performed by the user through the touch screen or touchpad of the electronic device 100, or operations performed by the user through voice commands or air gestures. The embodiments of the present application do not limit the implementation method of the user operations.

1A-1B exemplarily show the user interfaces involved in the process of taking a screenshot on the electronic device 100 through an application of a client operating system.

Referring to FIG. 1A , the user interface 110 may be a user interface of the host operating system (also referred to as a desktop). The user interface may include one or more application icons (e.g., an icon of a “recycle bin” application, an icon of a “this computer” application, an icon of an “application market” application, an icon of a “reading” application, an icon of a “chat” application, etc.), and the one or more application icons may include icons of applications of the host operating system (e.g., an icon of a “recycle bin” application, an icon of a “this computer” application, an icon of an “application market” application), and icons of applications of the client operating system (e.g., an icon of a “reading” application, an icon of a “chat” application).

Optionally, the icon of the client operating system application may be displayed with a relevant identifier of the mobile device (eg, identifier 111, identifier 112), so that the user can easily distinguish whether the icon is an icon of the host operating system application or an icon of the client operating system application.

1A, the user interface 110 may also include a user interface of one or more applications of the client operating system opened by the user (eg, user interface 113). It can be seen that the user interface 113 is a user interface of a reading application of the client operating system.

If the user wants to take a screenshot of the user interface 113, the electronic device 100 can detect the user's operation (such as a click operation) on the option 114 in the user interface 113. In response to the operation, the electronic device 100 can display the window 120 shown in Figure 1B.

Referring to Figure 1B, the window 120 may include one or more options (such as a "screenshot" option 121, etc.), and the electronic device 100 can detect the user's operation on the "screenshot" option 121 (such as a click operation). In response to the operation, the electronic device 100 can take a screenshot of the entire user interface 113. After the screenshot is completed, it can be saved as a picture in the "Gallery" application of the client operating system.

1C , the picture 130 shown in FIG1C can be a screenshot image generated by the screenshot process shown in FIG1A-FIG1B . It can be seen that the picture 130 is a screenshot image corresponding to the entire user interface 113 .

1D-1G exemplarily illustrate the user interfaces involved in the process of sharing screenshots by the electronic device 100 through an application of the client operating system.

Take the electronic device 100 sharing the picture 130 shown in FIG. 1C through the “chat” application (ie, an application with social functions) of the client operating system as an example.

Referring to FIG1D , the user interface 140 may be a user interface of a “chat” application of the client operating system. It can be seen that the user interface may be a chat interface between the user and his friend Lily. If the user wants to share a picture with his friend Lily, the electronic device 100 may detect the user's operation (e.g., a click operation) on the option 141 in the user interface 140. In response to the operation, the electronic device 100 displays the window 150 (i.e., the dotted box area) shown in FIG1E in the user interface 140.

Referring to FIG. 1E , window 150 may include options (e.g., option 151) corresponding to one or more pictures in the “Gallery” application, which can be used by the user to select one or more pictures to share. It can be seen that the option corresponding to the picture 130 exemplarily shown in FIG. 1C above is option 151, which is currently in an unselected state. If the user wants to share picture 130 with his friend Lily, then the electronic device 100 can detect the user's operation on option 151 (e.g., a click operation). In response to the operation, the electronic device 100 can set option 151 from the unselected state shown in FIG. 1E to the selected state shown in FIG. 1F , indicating that the picture selected by the user to be shared is picture 130.

Referring to FIG. 1F , after the user has selected the above-mentioned picture to be shared, the electronic device 100 can detect the user's operation (e.g., a click operation) on option 161. In response to the operation, the electronic device 100 can send the picture 130 to the electronic device of the friend Lily through the "chat" application, and display the chat message 171 shown in FIG. 1G in the user interface 140. The chat message can be a message for the user to share the picture 130 with his friend Lily. At this point, the process of sharing the screenshot is completed.

In the embodiment of the present application, the user interfaces of multiple applications of the client operating system can be displayed simultaneously. For example, the user interface of the "reading" application and the user interface of the "chatting" application shown in FIG. 1D can be displayed in parallel at the same time.

In some examples, during the screenshot sharing process shown in Figures 1D-1G above, the electronic device 100 may also only display the user interface of the "chat" application for sharing screenshots, without displaying the user interfaces of other applications (such as the user interface of the "reading" application).

As can be seen from Figures 1A-1G, in the screenshot process shown in Figures 1A-1B, the simulator is just a simple imitation of the screenshot function of the mobile device, and can only support the most basic fixed-size screenshot of the user interface of the application (that is, it can only capture the entire user interface of the application). The screenshot editing function is relatively simple, and the screenshot image will be saved in the "Gallery" application after the screenshot is completed. In the screenshot sharing process shown in Figures 1D-1G, the user needs to first select the screenshot image saved in the "Gallery" application, and then trigger the sharing operation after the selection is completed. The whole process is relatively complicated and the user experience is poor.

At present, the screenshot function provided by computer operating systems is much more powerful than that provided by mobile device operating systems. For computer operating systems, whether it is the screenshot function that comes with the system or the shortcut screenshot function provided by third-party applications installed in the computer operating system, both can provide image editing operations (such as free selection of screenshot area, text filling and annotation, free image editing, etc.) during the screenshot process, which is far superior to the screenshot function provided by mobile devices in terms of user experience.

In the ecological integration scenario, if the powerful screenshot function provided by the computer ecosystem can be shared with the mobile ecosystem of the simulator, users will have a better experience. Therefore, the current technology has also achieved the use of the screenshot function of the computer operating system (ie, the host operating system) to perform cross-system screenshot operations, that is, users can use the screenshot function provided by the computer operating system instead of the screenshot function provided by the simulator to perform screenshot operations. In this case, after the screenshot is completed, the screenshot data needs to be copied from the computer operating system to the "Gallery" application of the client operating system of the simulator. When the user wants to share the screenshot, it is the same as the aforementioned screenshot sharing process. The user needs to first select the screenshot saved in the "Gallery" application, and then trigger the sharing operation after the selection is completed. The entire process is also relatively complicated and the user experience is poor.

In short, the screenshot function provided by the current simulator is relatively simple. It cannot freely select the screenshot area like the screenshot function provided by the computer operating system, nor can it capture images beyond the entire user interface of the application. The editing function of the screenshot is simple, and the process of sharing screenshots is relatively complicated. As a product in the ecological integration scenario, it cannot fully utilize the advantages of the powerful screenshot function provided by the computer operating system, and the application integration experience of the computer operating system and the mobile operating system is poor.

Based on the above problems, an embodiment of the present application provides a screenshot sharing method, which is applied to an electronic device 100. The electronic device 100 can be installed with a host operating system (also referred to as a first operating system), and a client operating system (also referred to as a second operating system) can be loaded on the host operating system. After the electronic device 100 detects that the user triggers the operation of displaying the screenshot interface, the host operating system can support the user to freely perform image capture operations of any area, image editing operations, etc., thereby generating a screenshot image (i.e., a screenshot) and saving the information of the screenshot image to the clipboard of the host operating system. Afterwards, the host operating system can share the information of the screenshot image to the clipboard of the client operating system for use by the application of the client operating system, thereby achieving the effect that the application of the client operating system can directly paste the screenshot image. For social applications of the client operating system, a one-click cross-system screenshot sharing effect can also be achieved, thereby simplifying user operations and improving user experience.

It should be noted that the present application embodiment does not impose any restrictions on the operating system types of the host operating system and the client operating system. Operating system, the client operating system is The operating system is used as an example to illustrate the content of the embodiment of the present application. Those skilled in the art can understand that the embodiment of the present application can also be implemented with other operating systems, and the present application does not impose any limitation on this.

The electronic device 100 in the embodiment of the present application may be referred to as a host machine. The electronic device 100 may be a desktop computer, a laptop computer, etc., which is not limited in the embodiment of the present application. A host operating system may be installed on the electronic device 100, and a client operating system may be loaded on the host operating system. The host operating system may include but is not limited to operating system, Operating system. The client operating system may include but is not limited to operating system, operating system.

The screenshot sharing method provided in the embodiment of the present application can be implemented by installing a simulator on a computer (ie, a host machine). The embodiment of the present application does not limit the type of the simulator.

In some examples, the simulator may be Huawei's Mobile Application Engine.

A set of user interfaces involved in the process of implementing the screenshot sharing method provided in an embodiment of the present application is exemplarily introduced below in conjunction with FIG. 2A-FIG 2E.

2A-2B exemplarily show a set of user interfaces involved in the screenshot process of the screenshot sharing method provided in an embodiment of the present application.

Referring to FIG. 2A , user interface 210 (ie, screenshot interface) may be a user interface involved in the screenshot process of the screenshot sharing method provided in the embodiment of the present application.

The screenshot sharing method provided in the embodiment of the present application utilizes the screenshot function of the host operating system to complete the screenshot process, wherein the screenshot function of the host operating system can be a system-provided one (for example, provided by a system application) or provided by a third-party application installed by the host operating system, and the embodiment of the present application does not limit this.

The embodiment of the present application does not limit the way in which the user triggers the display of the user interface 210 shown in Figure 2A. For example, it can be triggered by a shortcut key on the keyboard of the electronic device 100; for another example, it can be triggered by the touch screen, touchpad or mouse of the electronic device 100; for another example, it can be triggered by the user's voice command operation or air gesture; and so on.

In some examples, the user interface 210 exemplarily shown in FIG. 2A may be triggered to be displayed after the user performs an operation (eg, clicks) on the “screenshot” option in the window 120 exemplarily shown in FIG. 1B .

Continuing to refer to FIG. 2A , the user interface 210 may include a screenshot area 220 and a window 230 .

Among them, the screenshot area 220 can be freely selected by the user, that is, after the user triggers the display of the user interface 210, the host operating system can support the user to freely select the screenshot area in the user interface 210, which is flexible and convenient, and improves the user experience. For example, as shown in FIG2A, not only can the user be supported to capture the user interface of the application of the client operating system (such as the user interface of the "Reading" application in the screenshot area 220 in FIG2A), but the user can also be supported to capture any user interface displayed by the host operating system (such as the blank user interface in the screenshot area 220 in FIG2A except the user interface of the "Reading" application, that is, a part of the user interface of the desktop).

Taking the screenshot area 220 as an example, after the user selects the screenshot area, a plurality of boundary points (also referred to as marking points) may be displayed on the four boundary lines of the screenshot area 220, such as boundary point 221, boundary point 222, boundary point 223, boundary point 224, boundary point 225, boundary point 226, boundary point 227, and boundary point 228. These boundary points may be used to adjust the size of the screenshot area 220. The user may expand or reduce the screenshot area 220 in different directions by dragging these boundary points.

The boundary point 221 can be used by the user to expand the screenshot area 220 to the upper left or to reduce it to the lower right. For example, the user can drag the boundary point 221 to the upper left to expand the screenshot area 220 to the upper left; for another example, the user can drag the boundary point 221 to the lower right to reduce the screenshot area 220 to the lower right.

The boundary point 222 can be used by the user to expand the screenshot area 220 upward or reduce it downward. For example, the user can drag the boundary point 222 upward to expand the screenshot area 220 upward; for another example, the user can drag the boundary point 222 downward to reduce the screenshot area 220 downward.

The boundary point 223 can be used by the user to expand the screenshot area 220 to the upper right or to reduce it to the lower left. For example, the user can drag the boundary point 223 to the upper right to expand the screenshot area 220 to the upper right; for another example, the user can drag the boundary point 223 to the lower left to reduce the screenshot area 220 to the lower left.

The boundary point 224 can be used by the user to expand the screenshot area 220 to the right or to shrink it to the left. For example, the user can drag the boundary point 224 to the right to expand the screenshot area 220 to the right; for another example, the user can drag the boundary point 224 to the left to shrink the screenshot area 220 to the left.

The boundary point 225 can be used by the user to expand the screenshot area 220 to the lower right or to shrink it to the upper left. For example, the user can drag the boundary point 225 to the lower right to expand the screenshot area 220 to the lower right; for another example, the user can drag the boundary point 225 to the upper left to shrink the screenshot area 220 to the upper left.

The boundary point 226 can be used by the user to expand the screenshot area 220 directly downward or shrink it directly upward. For example, the user can drag the boundary point 226 directly downward to expand the screenshot area 220 directly downward; for another example, the user can drag the boundary point 226 directly upward to shrink the screenshot area 220 directly upward.

The boundary point 227 can be used by the user to expand the screenshot area 220 to the lower left or to shrink it to the upper right. For example, the user can drag the boundary point 227 to the lower left to expand the screenshot area 220 to the lower left; for another example, the user can drag the boundary point 227 to the upper right to shrink the screenshot area 220 to the upper right.

The boundary point 228 can be used by the user to expand the screenshot area 220 to the left or to reduce it to the right. For example, the user can drag the boundary point 228 to the left to expand the screenshot area 220 to the left; for another example, the user can drag the boundary point 228 to the right to reduce the screenshot area 220 to the right.

The window 230 may include one or more options, for example, option 231, option 232, option 233, option 234, option 235, option 236, option 237, option 238, option 239, option 240, option 241, option 242, option 243, option 244, option 245, option 246, option 247, option 248, option 2 235, Option 236, Option 237, Option 238, Option 239, Option 240.

Option 231 can be used to add a box mark in the screenshot area 220 and freely select any area in the screenshot area 220.

Option 232 can be used to add an elliptical frame annotation in the screenshot area 220 and freely select any area in the screenshot area 220.

Option 233 may be used to add an arrow annotation to the screenshot area 220 .

Option 234 may be used to add a pen annotation (eg, a highlighter annotation) to the screenshot area 220 .

Option 235 may be used to add a mosaic annotation to the screenshot area 220 .

Option 236 may be used to add a text annotation to the screenshot area 220 .

Option 237 may be used to undo the annotation added in the screenshot area 220 .

Option 238 can be used to save the screenshot image of the screenshot area 220 (including the user interface displayed on the screen and the annotations added by the user), that is, to save the screenshot image of the screenshot area 220 as a file with a customizable file name.

Option 239 can be used to exit the screenshot, that is, cancel the display of the current screenshot interface, and will not save the screenshot image of the screenshot area 220, nor will it save the screenshot image of the screenshot area 220 to the clipboard.

Option 240 can be used to complete the screenshot, that is, cancel the display of the current screenshot interface and save the screenshot image of the screenshot area 220 to the clipboard.

That is to say, these options in the window 230 can be used to support the user to perform various editing operations in the screenshot area 220, thereby meeting the personalized needs of the user.

For example, referring to FIG2B , it can be seen that the user has performed a variety of editing operations in the screenshot area, such as adding a brush annotation, a box annotation, and a text annotation. Further, if the user wants to save the screenshot image in FIG2B to the clipboard, then the electronic device 100 can detect the user's operation (such as a click operation) on option 240 in FIG2B , and in response to the operation, the electronic device 100 can save the screenshot image in FIG2B to the clipboard.

Referring to FIG. 2C , the exemplary picture 250 shown in FIG. 2C may be a screenshot image generated by the screenshot process shown in FIG. 2A-FIG. 2B . It can be seen that, unlike the picture 130 in FIG. 1C , the picture 250 includes not only the captured user interface of the application program of the client operating system, but also the user interface other than the user interface of the application program of the client operating system, and also includes annotations added by the user. In this way, the powerful screenshot editing function provided by the host operating system is fully utilized, so as to meet the personalized needs of users and improve the user experience.

2D-2E exemplarily illustrate a set of user interfaces involved in the screenshot sharing process of the screenshot sharing method provided in an embodiment of the present application.

Take the example of electronic device 100 sharing the picture 250 shown in FIG. 2C through the "chat" application (i.e., an application with social functions) of the client operating system. It is not limited to this, and it can also be other applications with the ability to share screenshots, which is not limited in the present embodiment of the application.

Referring to Fig. 2D, user interface 260 can be a user interface of a "chat" application program of a client operating system. It can be seen that the user interface can be a chat interface between the user and his friend Lily.

In an embodiment of the present application, after the user completes the screenshot process shown in the above-mentioned Figures 2A-2B, the electronic device 100 can automatically complete the cross-system clipboard content sharing (that is, share the content in the clipboard of the host operating system to the clipboard of the client operating system), that is, the electronic device 100 can share the information of the screenshot image generated by the screenshot process shown in Figures 2A-2B saved in the clipboard of the host operating system to the clipboard of the client operating system.

Among them, the specific implementation process of the above-mentioned "electronic device 100 automatically completes cross-system clipboard content sharing" will be introduced in detail in subsequent embodiments and will not be expanded here.

Continuing to refer to Figure 2D, after automatically completing the sharing of clipboard content across systems, the electronic device 100 can automatically trigger the display of a floating window 261 in the user interface 260 based on the information of the screenshot image shared by the above-mentioned host operating system. The window can include pictures that the user may want to send, and the picture can be a screenshot image generated by the host operating system, such as the picture 250 shown in the above-mentioned Figure 2C.

Continuing to refer to FIG. 2D , if the user wants to share the picture 250 in the floating window 261 with his friend Lily, then the electronic device 100 can detect the user's operation on the floating window 261 (e.g., a click operation on the picture 250 in the floating window 261), and in response to the operation, the electronic device 100 can send the picture 250 to the electronic device of the friend Lily through the "chat" application, and display the chat message 271 shown in FIG. 2E in the user interface 260, which can be a message for the user to share the picture 250 with his friend Lily. At this point, the process of sharing the screenshot is completed.

The above is to trigger the sending of the screenshot by the user operating the floating window. In some examples, the sending of the screenshot can also be triggered by other methods. For example, the user directly triggers the display of the paste option by right-clicking the mouse in the input box, and clicks the paste option to display the screenshot in the input box. Then the user clicks the send option to complete the process of sharing the screenshot. For another example, the user can also directly Then use the shortcut keys on the keyboard to paste the screenshot in the input box. In this way, the screenshot can be displayed in the input box, and then the user clicks the send option to complete the process of sharing the screenshot.

It can be seen from the screenshot sharing process shown in Figures 2D-2E that, unlike the screenshot sharing process shown in the aforementioned Figures 1D-1G, after completing the screenshot process, the user no longer needs to manually select the screenshot image to be shared in the "Gallery" application, but the electronic device 100 can automatically trigger the screenshot sharing action (for example, automatically trigger the display of the floating window 261 shown in Figure 2D). In this way, the user only needs one step (for example, a click operation on the picture 250 in the floating window 261) to complete the screenshot sharing process, thereby achieving the effect of one-click screenshot sharing, simplifying user operations, and improving user experience.

In some examples, during the screenshot sharing process shown in Figures 2D-2E above, the electronic device 100 may also only display the user interface of the "chat" application for sharing screenshots, without displaying the user interfaces of other applications (such as the user interface of the "reading" application).

In the embodiment of the present application, the electronic device 100 can simultaneously display the user interfaces of multiple applications of the client operating system. The above-mentioned Figures 2A to 2E are only used to capture the user interface of an application of the client operating system as an example to illustrate the process of implementing the screenshot sharing method provided in the embodiment of the present application. It is easy to understand that the screenshot sharing method provided in the embodiment of the present application can also be applied to the scenario of capturing the user interfaces of multiple applications of the client operating system. The process of implementing the screenshot sharing method provided in the embodiment of the present application is illustrated below in conjunction with Figures 3A to 3F by taking the user interfaces of two applications of the client operating system as an example.

Another set of user interfaces involved in the process of implementing the screenshot sharing method provided in the embodiment of the present application is exemplarily introduced below in conjunction with FIG. 3A-FIG .

3A-3C exemplarily illustrate another set of user interfaces involved in the screenshot process of the screenshot sharing method provided in an embodiment of the present application.

3A , user interface 310 may be a user interface of an application of the client operating system (eg, a user interface of a “Shopping 1” application), and user interface 320 may be a user interface of another application of the client operating system (eg, a “Shopping 2” application).

If the user wants to take a screenshot, the electronic device 100 may detect an operation by the user to trigger the display of a screenshot interface, and in response to the operation, the electronic device 100 may display the user interface 330 exemplarily shown in FIG. 3B .

Referring to FIG. 3B , the user interface 330 (ie, the screenshot interface) may be a user interface involved in the screenshot process of the screenshot sharing method provided in the embodiment of the present application.

The embodiment of the present application does not limit the implementation method of the above-mentioned "user triggering the operation of displaying the screenshot interface". For example, the user may trigger the operation of displaying the screenshot interface through a shortcut key on the keyboard of the electronic device 100; for another example, the user may trigger the operation of displaying the screenshot interface through the touch screen, touchpad or mouse of the electronic device 100; for another example, the user may trigger the operation of displaying the screenshot interface through a voice command or a gesture in the air; and so on.

In some examples, since user interface 310 and user interface 320 are similar to user interface 113 shown in FIG1A above, the “screenshot” option in window 120 shown in FIG1B can also be displayed through operation option 114. Therefore, the above-mentioned “user triggering operation to display the screenshot interface” can also be the user’s operation (such as a click operation) on the “screenshot” option in window 120 displayed on user interface 310 or user interface 320.

Continuing to refer to FIG. 3B , the user interface 330 may include a screenshot area 340 and a window 350 .

Among them, the screenshot area 340 can be freely selected by the user, that is, after the user triggers the display of the user interface 330, the host operating system can support the user to freely select the screenshot area in the user interface 330, which is flexible and convenient, and improves the user experience. For example, as shown in FIG3B, not only can the user be supported to capture the user interface of the application of the client operating system (such as the user interface of the "Shopping 1" application and the user interface of the "Shopping 2" application in the screenshot area 340 in FIG3B), but the user can also be supported to capture any user interface displayed by the host operating system (such as the blank user interface in the screenshot area 340 in FIG3B except the user interface of the "Shopping 1" application and the user interface of the "Shopping 2" application, that is, a part of the user interface of the desktop).

Taking the screenshot area 340 as an example, after the user selects the screenshot area, a plurality of boundary points (also referred to as marking points) may be displayed on the four boundary lines of the screenshot area 340, and these boundary points may be used to adjust the size of the screenshot area 340. The user may expand or reduce the screenshot area 340 in different directions by dragging these boundary points.

The specific function of each boundary point of the screenshot area 340 can be referred to the aforementioned description of each boundary point of the screenshot area 220. The relevant text description of the point will not be repeated here.

The options in window 350 may be used to support the user in performing various editing operations in the screenshot area 340 .

For the specific functions of each option in window 350 , reference may be made to the aforementioned text descriptions of each option in window 230 , which will not be repeated here.

For example, referring to FIG3C , it can be seen that the user has performed multiple editing operations in the screenshot area, for example, the user has added a box annotation in the "Shopping 1" application in the screenshot area, and has also added a box annotation in the "Shopping 1" application in the screenshot area. Further, if the user wants to save the screenshot image in FIG3C to the clipboard, then the electronic device 100 can detect the user's operation (such as a click operation) on option 351 in FIG3C , and in response to the operation, the electronic device 100 can save the screenshot image in FIG3C to the clipboard.

Referring to FIG. 3D , the exemplary picture 360 shown in FIG. 3D may be a screenshot image generated by the screenshot process shown in FIG. 3A to FIG. 3C . It can be seen that, unlike the picture 130 in FIG. 1C , the picture 360 includes not only the user interfaces of multiple applications of the client operating system that have been captured, but also the user interfaces other than the user interfaces of the applications of the client operating system, and also includes annotations added by the user. In this way, the powerful screenshot editing function provided by the host operating system is fully utilized, thereby meeting the personalized needs of users and improving the user experience.

3E-3F exemplarily illustrate another set of user interfaces involved in the screenshot sharing process of the screenshot sharing method provided in an embodiment of the present application.

Take the example of electronic device 100 sharing the picture 360 shown in Figure 3D through the "chat" application (i.e., an application with social functions) of the client operating system. It is not limited to this, and can also be other applications with the ability to share screenshots, which is not limited in this embodiment of the present application.

Referring to Fig. 3E, user interface 370 can be a user interface of a "chat" application program of a client operating system. It can be seen that the user interface can be a chat interface between the user and his friend Lily.

In an embodiment of the present application, after the user completes the screenshot process shown in Figures 3A-3C above, the electronic device 100 can automatically complete the cross-system clipboard content sharing (that is, share the content in the clipboard of the host operating system to the clipboard of the client operating system), that is, the electronic device 100 can share the information of the screenshot image generated by the screenshot process shown in Figures 3A-3C saved in the clipboard of the host operating system to the clipboard of the client operating system.

Continuing to refer to Figure 3E, after automatically completing the sharing of clipboard content across systems, the electronic device 100 can automatically trigger the display of a floating window 371 in the user interface 370 based on the information of the screenshot image shared by the above-mentioned host operating system. The window can include pictures that the user may want to send, and the picture can be a screenshot image generated by the host operating system, such as the picture 360 shown in the above-mentioned Figure 3D.

Continuing to refer to FIG. 3E , if the user wants to share the picture 360 in the floating window 371 with his friend Lily, then the electronic device 100 can detect the user's operation on the floating window 371 (e.g., a click operation on the picture 360 in the floating window 371), and in response to the operation, the electronic device 100 can send the picture 360 to the electronic device of the friend Lily through the "chat" application, and display the chat message 381 shown in FIG. 3F in the user interface 370, which can be a message for the user to share the picture 360 with his friend Lily. At this point, the process of sharing the screenshot is completed.

The above is a way of triggering the sending of screenshots by the user operating the floating window. In some examples, the sending of screenshots can also be triggered in other ways. For example, the user directly triggers the display of the paste option by right-clicking the mouse in the input box, and clicks the paste option to display the screenshot in the input box. The user then clicks the send option to complete the process of sharing the screenshot. For another example, the user can also directly paste the screenshot in the input box through the shortcut keys on the keyboard. In this way, the screenshot can be displayed in the input box, and the user then clicks the send option to complete the process of sharing the screenshot.

It can be seen from the screenshot sharing process shown in Figures 3E-3F that, unlike the sharing process shown in the aforementioned Figures 1D-1G, after completing the screenshot process, the user no longer needs to manually select the screenshot image to be shared in the "Gallery" application, but the electronic device 100 can automatically trigger the screenshot sharing action (for example, automatically trigger the display of the floating window 371 shown in Figure 3E). In this way, the user only needs one step (for example, a click operation on the picture 360 in the floating window 371) to complete the screenshot sharing process, thereby achieving the effect of one-click screenshot sharing, simplifying user operations, and improving user experience.

In some examples, during the process of sharing the screenshots shown in FIG. 3E-FIG 3F, the electronic device 100 may also only display the above-mentioned The user interface of the “Chat” application in the screenshot is shared, while the user interfaces of other applications (such as the user interface of the “Shopping 1” application and the user interface of the “Shopping 2” application) are not displayed.

It is easy to understand that in the embodiment of the present application, the user can capture any user interface displayed on the electronic device 100. In the above Figures 2A-2B and 3A-3C, only the user captures the user interface of the open application of the client operating system and the desktop of the host operating system as an example. The present application is not limited to this. The user can also capture other user interfaces, for example, the user interface of the application of the host operating system. This embodiment of the present application is not limited to this.

The following describes a specific process of a screenshot sharing method provided in an embodiment of the present application.

FIG4 exemplarily shows a specific process of a screenshot sharing method provided in an embodiment of the present application.

Referring to FIG. 4 , the method can be applied to an electronic device 100 . The electronic device 100 can be installed with a host operating system, and a client operating system can be loaded on the host operating system. The specific steps of the method are described in detail below:

S401-S403, the host operating system detects that the user triggers an operation to display a screenshot interface. In response to the operation, the host operating system can display the screenshot interface and detect the user's screenshot operation on the screenshot interface. In response to the operation, the host operating system generates a screenshot image 1 and saves the information of the screenshot image 1 to the clipboard of the host operating system.

Among them, the above-mentioned "operation of the user triggering the display of the screenshot interface" can be the user triggering the operation of displaying the screenshot interface through the shortcut key on the keyboard of the electronic device 100, or the user triggering the operation of displaying the screenshot interface through the touch screen, touchpad or mouse of the electronic device 100, or the user's voice command or air gesture to trigger the operation of displaying the screenshot interface, etc., the embodiment of the present application is not limited to this.

The “screenshot interface” mentioned above may be a user interface for performing a screenshot operation (eg, the user interface 210 in FIG. 2A , or the user interface 330 in FIG. 3B ).

Among them, the above-mentioned "screenshot operation" can be an operation in which the user selects a screenshot area (for example, selects the screenshot area 220 in Figure 2A, or selects the screenshot area 340 in Figure 3B) and completes the screenshot (for example, clicks option 240 in Figure 2B, or clicks option 351 in Figure 3C); or, the user selects the screenshot area and edits the image of the screenshot area (for example, adding a box annotation, adding an ellipse box annotation, adding an arrow annotation, adding a brush annotation, adding a mosaic annotation, adding a text annotation, etc.), and then completes the screenshot operation.

The “screenshot image 1 ” mentioned above may be generated after the user performs a screenshot operation (eg, the image 250 in FIG. 2C , or the image 360 in FIG. 3D ).

After generating the screenshot image 1 , the host operating system may save the information of the screenshot image 1 to the clipboard of the host operating system.

The above-mentioned “information of screenshot image 1 ” may include image data of screenshot image 1 , description information (such as data name, data type, data size, data generation time, etc.), etc.

In some examples, the information of the screenshot image 1 is saved in the clipboard of the host operating system, and specifically, the image data of the screenshot image 1 is saved in the clipboard of the host operating system. The image data of the screenshot image 1 may be the image data of the original image of the screenshot image 1.

S404-S405, the host operating system determines whether the latest content saved in the clipboard is a picture. If so, the information of the screenshot image 1 is saved in the shared folder. If not, the subsequent steps are not executed.

Specifically, the host operating system can monitor in real time whether the content in its clipboard has changed. When it detects that the content in its clipboard has changed, the host operating system can determine whether the latest content saved in the clipboard is a picture. Taking the latest content saved in the clipboard as the above-mentioned screenshot image 1 as an example, the host operating system can determine that screenshot image 1 is a picture. After that, the host operating system can save the information of screenshot image 1 to the shared folder.

The shared folder may be a folder that both the host operating system and the client operating system have access rights to.

The shared folder can be a folder in the host operating system or a folder in the client operating system. The data in the shared folder can be stored by a shared data storage module, which will be described in the following embodiments and will not be expanded here.

In an embodiment of the present application, file sharing between the client operating system and the host operating system can be achieved based on a file system service of a shared folder. For example, the file system service can be 9p-virtio (Plan 9 folders sharing over Virtio-I/O virtualization framework).

When the host operating system determines that the most recently saved content in the clipboard is not a picture, the host operating system may not execute subsequent steps.

S406 . The host operating system sends a message 1 to the guest operating system. The message is used to instruct the guest operating system to obtain information of the screenshot image 1 .

Specifically, after saving the information of the screenshot image 1 in the shared folder, the host operating system may send a message 1 to the client operating system, where the message is used to instruct the client operating system to obtain the information of the screenshot image 1 .

That is, the host operating system can send message 1 to notify the client operating system that there is new content saved in the clipboard of the host operating system to be shared with the client operating system, and the client operating system can obtain the new content saved in the clipboard of the host operating system from the shared folder.

Among them, the above message 1 can be a message sent through inter-process communication (IPC). In the embodiment of the present application, the inter-process communication can be implemented by using a pipe, but is not limited to this, and can also be implemented in other ways, which is not limited in the embodiment of the present application.

S407-S408, the client operating system obtains information of the screenshot image 1. Afterwards, the client operating system saves the information of the screenshot image 1 to the clipboard of the client operating system.

Specifically, after receiving the message 1 sent by the host operating system, the client operating system can obtain the information of the screenshot image 1 based on the message 1, for example, obtaining the information of the screenshot image 1 from the shared folder of the electronic device 100. After obtaining the information of the screenshot image 1, the client operating system can save the information of the screenshot image 1 to the clipboard of the client operating system so that the subsequent application of the client operating system can use it.

In some examples, the information of the screenshot image 1 is saved in the clipboard of the client operating system, and specifically, the image data of the screenshot image 1 is saved in the clipboard of the client operating system. The image data of the screenshot image 1 may be the image data of the original image of the screenshot image 1.

S409-S410, the client operating system determines whether the latest content saved in the clipboard is a picture. If so, it scans the path of the screenshot image 1 in the shared folder and inserts the information of the screenshot image 1 into the media database based on the above path. If not, the subsequent steps are not executed.

Specifically, the client operating system can monitor in real time whether the content in its clipboard has changed. When it detects that the content in its clipboard has changed, the client operating system can determine whether the latest content saved in the clipboard is a picture. Taking the latest content saved in the clipboard as the above-mentioned screenshot image 1 as an example, the client operating system can determine that screenshot image 1 is a picture. After that, the client operating system can scan the path of screenshot image 1 in the shared folder, and can insert the information of screenshot image 1 into the media database based on the above-mentioned path, that is, insert the information of screenshot image 1 into the media database as a database record.

In some examples, the client operating system inserts the information of the screenshot image 1 into the media database based on the above path. Specifically, the client operating system may insert the information of the screenshot image 1 into the media database when it determines that the screenshot image 1 meets the preset rules based on the above path.

Among them, the above-mentioned "preset rules" may include but are not limited to preset screenshot rules, wherein the "preset screenshot rules" may refer to preset rules for determining whether the content saved in the clipboard is a screenshot image, and the above-mentioned "preset screenshot rules" may include but are not limited to: the naming of the screenshot image 1 includes specific keywords (such as keywords such as "screenshot"), and the time interval between the time point recorded in the timestamp information of the screenshot image 1 (that is, the timestamp information generated by the screenshot image 1) and the current time point (that is, the time point of scanning the path of the screenshot image 1) is within a preset time interval (for example, 10 seconds, 20 seconds, etc.).

Among them, multiple fields can be used to record data in the data table of the media database. These multiple fields may include but are not limited to: _id (i.e., the serial number inserted into the media database, increasing from 1), _data (absolute path of the file), _size (size of the file), _display_name (file name with extension), mime_type (Multipurpose Internet Mail Extension type, consisting of two parts: data category/specific category under the category), title (file name without extension).

Exemplarily, assuming that there is already 1 record in the media database when the above-mentioned “information of screenshot image 1” is inserted into the media database, then the _id of the record corresponding to the above-mentioned “information of screenshot image 1” is 2. Assuming that the absolute path of the above-mentioned “screenshot image 1” is /storage/emulated/0/PC shared folder/Screenshot/Screenshot_20220429_161813.png, and the size is 359238KB, then the _data of the record corresponding to the above-mentioned “information of screenshot image 1” is “/storage/emulated/0/PC shared folder/Screenshot/Screenshot_20220429_161813.png”, _size is “359238”, _display_name is “Screenshot_20220429_161813.png”, mime_type is “image/png”, and title is “Screenshot_20220429_161813”.

When the client operating system determines that the most recently saved content in the clipboard is not an image, the client operating system may not execute subsequent steps. Steps.

In some examples, the information of screenshot image 1 is inserted into the media database. Specifically, the description information of screenshot image 1 (such as data name, data type, data size, data generation time, etc.) is inserted into the media database, thereby generating a database record so that subsequent applications can detect that a new database record has been inserted into the media database.

S411 , the client operating system detects an operation of a user opening the user interface 1 of the client operating system's application program 1 .

Among them, application 1 can be a social application (such as the aforementioned "chat" application) as an example, and the user interface 1 of application 1 can be a user interface of application 1 for chatting with friends (such as the user interface 260 of the "chat" application in the aforementioned Figure 2D, or the user interface 370 of the "chat" application in Figure 3E).

It is easy to understand that the screenshot sharing method proposed in the embodiment of the present application can only be executed when the user interface 1 of the above-mentioned application 1 meets the conditions for sharing screenshots, wherein the "conditions for sharing screenshots" may include but are not limited to: an input box is displayed in the user interface 1 of the application 1, controls that can be used for file sharing are displayed, and so on.

It should be noted that the embodiment of the present application does not limit the execution time sequence of the above step S411. For example, the above step S411 can be executed after the user completes the screenshot operation, or before the user triggers the operation of displaying the screenshot interface.

S412 , application 1 obtains information of screenshot image 1 from the clipboard of the client operating system.

Specifically, since the client operating system has saved the information of the screenshot image 1 to the clipboard of the client operating system, after detecting the user's operation of opening the user interface 1 of the client operating system's application 1, the application 1 can obtain the information of the screenshot image 1 from the clipboard of the client operating system.

In some examples, when application 1 is in operation or when application 1 is displaying user interface 1, application 1 can monitor whether the content in the media database of the client operating system has changed. When it is determined that the content in the media database has changed, application 1 can obtain the changed content from the clipboard of the client operating system. Assuming that the changed content (i.e., the content most recently inserted into the media database) is the information of the aforementioned screenshot image 1, since the client operating system has saved the information of the screenshot image 1 to the clipboard of the client operating system, application 1 can obtain the information of the screenshot image 1 from the clipboard of the client operating system.

It is understandable that after the client operating system saves the information of the screenshot image 1 to the clipboard, it can also insert the information of the screenshot image 1 into the media database in order to automatically trigger the screenshot sharing action. Because the application 1 can monitor whether the content in the media database has changed, in this way, when the content in the media database is monitored to have changed, the application 1 can trigger the display of a floating window (such as the floating window 1 shown in the following step S413), that is, automatically trigger the screenshot sharing action, so as to achieve the purpose of one-click screenshot sharing.

In some examples, before the above-mentioned "application 1 obtains the information of screenshot image 1 from the clipboard of the client operating system", application 1 can also determine whether the changed content in the media database complies with preset rules (such as preset screenshot rules). If so, the information of screenshot image 1 is obtained from the clipboard of the client operating system. If not, the information of screenshot image 1 is not obtained from the clipboard of the client operating system, and the subsequent steps are not executed.

Among them, the above-mentioned preset rules may include but are not limited to: the naming of the screenshot image 1 includes specific keywords (such as keywords such as "screenshot"), and the time interval between the time point recorded in the timestamp information of the screenshot image 1 (such as "20220429_161813") and the current time point (that is, the time point when the application 1 determines whether the content that has changed in the media database complies with the preset rules) is within a certain preset time interval (such as 10 seconds, 20 seconds, etc.).

S413 . Application 1 displays floating window 1 in user interface 1 . The floating window is generated based on screenshot image 1 .

Specifically, after the application 1 obtains the information of the screenshot image 1 from the clipboard of the client operating system, the application 1 may generate and display the floating window 1 based on the screenshot image 1 in the user interface 1 .

Exemplarily, the floating window 1 may be the floating window 261 in FIG. 2D , and the screenshot image 1 may be the picture 250 in FIG. 2C .

Exemplarily, the floating window 1 may also be the floating window 371 in FIG. 3E , and the screenshot image 1 may be the picture 360 in FIG. 3D .

It should be noted that the image displayed in the above floating window 1 can be a thumbnail of the screenshot image 1 or the original image of the screenshot image 1, and the embodiment of the present application does not limit this. It is easy to understand that the thumbnail of the screenshot image 1 is also generated based on the image data of the screenshot image 1 saved in the clipboard.

S414-S415, the client operating system detects the user's operation on the floating window 1, and in response to the operation, the client operating system can The electronic device 200 (eg, a friend's electronic device) sends the screenshot image 1 .

It is easy to understand that the client operating system sends the screenshot image 1 to the electronic device 200 (for example, a friend's electronic device). Specifically, the client operating system sends the screenshot image 1 to the electronic device 200 (for example, a friend's electronic device) through the hardware communication module provided by the electronic device 100.

By implementing the method provided by the embodiment shown in FIG. 4 above, when the electronic device 100 is installed with a host operating system and a client operating system is loaded on the host operating system, after detecting that the user triggers a screenshot operation, the electronic device 100 can support the user to freely perform image capture operations and image editing operations in any area through the host operating system, thereby generating a screenshot image. Furthermore, the electronic device 100 can save the information of the screenshot image to the clipboard of the host operating system. After that, the host operating system can also share the information of the screenshot image to the clipboard of the client operating system to achieve cross-system image transmission. The entire process does not require the user to manually save and copy the screenshot image data, and when the user shares the screenshot image, there is no need for complicated manual selection, sharing and other steps. Simplifying user operations can effectively improve the user experience of using the simulator, so that the user cannot perceive the differences between systems in the ecological integration scenario, thereby improving the competitiveness of ecological integration products.

In some examples, the screenshot image 1 in FIG. 4 can also be viewed in the "Gallery" application. In this case, when the user shares the screenshot image 1 with friends, the user can first select the screenshot image 1 in the "Gallery" application and then share the screenshot image 1, as in the screenshot sharing process shown in FIG. 1D to FIG. 1G. The "Gallery" application can obtain the path of the screenshot image 1 in the shared folder based on the information of the screenshot image 1 recorded in the media database and display the screenshot image 1.

In some examples, the information of the screenshot image 1 in FIG. 4 may also be sent by the host operating system to the client operating system through the message 1 in the aforementioned step S406, that is, the message 1 may include the information of the screenshot image 1. In this case, after receiving the message 1, the client operating system may save the information of the screenshot image 1 included in the message 1 to its clipboard, and after determining that the information of the screenshot image 1 meets the preset screenshot rule, insert it into the media database, and then execute the subsequent steps. Optionally, in the above case, the host operating system may not save the information of the screenshot image 1 to the shared folder.

In some examples, if a user copies a piece of plain text using the host operating system, the host operating system can save the text to the clipboard and determine that the latest content saved in the clipboard is not a picture but text. In this case, the host operating system can also send the text information to the client operating system, for example, in the form of an IPC message to the client operating system. The client operating system can save the text to the clipboard, so that the application of the client operating system can directly use the text.

The following introduces a software structure of an electronic device 100 provided in an embodiment of the present application.

FIG. 5 exemplarily shows a software structure of an electronic device 100 provided in an embodiment of the present application.

As shown in FIG5 , the software structure of the electronic device 100 may include a user space and a kernel space. Taking the operating system as an example, the software structure of the electronic device 100 is exemplified. The operating system is an example of the software environment required for the technical solution of the embodiment of the present application. Those skilled in the art can understand that the embodiment of the present application can also be implemented with other operating systems.

The user space may include: a screenshot application, a clipboard management module (ClipboardManager), a clipboard service module (ClipboardService), and a clipboard listening module (ClipboardListener). Among them:

The screenshot application may be an application that can provide a screenshot function. The application may be a system-provided application or a third-party application installed by the system, which is not limited in the present embodiment of the application.

In an embodiment of the present application, the screenshot application can support users to freely perform image capture operations of any area, edit images, etc.

The clipboard management module can be used to provide an interface for the application to call clipboard related services. For example, the application can obtain the content saved in the following clipboard service module by calling the clipboard management module to implement the paste function; for another example, the application can save the copied content to the following clipboard service module by calling the clipboard management module to implement the copy function.

The clipboard service module can be used to provide clipboard related services. For example, the clipboard service module can save the content copied by the user (such as text, screenshot images, etc.); for another example, the clipboard service module can determine whether the content copied by the user is a picture (such as a screenshot image, etc.); for another example, the clipboard service module can also send the information of the saved picture (such as a screenshot image, etc.) to the shared data storage module described below, so that the shared data storage module can save the information of the picture; and so on. It is easy to understand that saving data to the clipboard service module That is, you can think of it as saving the data to the clipboard.

The clipboard listening module can be used to monitor whether the content in the clipboard has changed (i.e., whether the content saved in the clipboard service module has changed); it can also be used to send an IPC message to the client operating system through the following inter-process communication module after detecting that the content in the clipboard has changed; and so on.

The kernel space may include: a shared data storage module and an inter-process communication module.

The shared data storage module can be used to store shared data (ie, data that both the host operating system and the client operating system have the right to access). For example, the shared data storage module can receive information about a picture sent by the clipboard service module and store the information about the picture.

A portion of the shared data storage module may be contained in user space.

It is easy to understand that all files in the "shared folder" in the above-mentioned embodiment can be stored in the shared data storage module.

The inter-process communication module can be used to implement the function of communicating between two processes. For example, the inter-process communication module can send an IPC message to the client operating system after the clipboard listening module detects that the content in the clipboard has changed.

The following introduces the software structure of another electronic device 100 provided in an embodiment of the present application.

FIG. 6 exemplarily shows a software structure of another electronic device 100 provided in an embodiment of the present application.

As shown in FIG6 , the software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. Taking the operating system as an example, the software structure of the electronic device 100 is exemplified. The operating system is an example of the software environment required for the technical solution of the embodiment of the present application. Those skilled in the art can understand that the embodiment of the present application can also be implemented with other operating systems.

The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. The operating system is divided into four layers, from top to bottom: application layer, application framework layer, system service layer, and kernel layer.

The application layer can include a series of application packages.

As shown in FIG. 6 , the application package may include applications such as camera, gallery, calendar, call, map, chat, WLAN, Bluetooth, music, video, short message, etc.

Among them, the chat application can be a social application that can realize multiple functions. For example, it can be used for users to share data (such as pictures, texts, etc.) with other users who use the application; for another example, it can be used for users to receive data (such as pictures, texts, etc.) shared by other users who use the application; for another example, the chat application can also monitor changes in the content of the media database; for another example, the chat application can read the information in the clipboard; and so on.

It should be noted that the name of the chat application is only a term used in the embodiment of the present application. The meaning it represents has been recorded in the embodiment of the present application, and its name does not constitute any limitation to the embodiment of the present application.

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

As shown in FIG. 6 , the application framework layer may include a window manager, a view system, a resource manager, a notification manager, a clipboard management module (ClipboardManager), and the like.

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

The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

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

The notification manager allows applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of an icon or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, it can prompt text information in the status bar and emit a prompt sound.

The Clipboard Manager module (ClipboardManager) can be used to provide applications with interfaces for calling clipboard-related services. For example, an application can obtain the content saved in the following clipboard service module by calling the Clipboard Manager module to implement the paste function; for another example, an application can save the copied content to the following clipboard service module by calling the Clipboard Manager module to implement the copy function.

The system service layer can include multiple functional modules. For example: surface manager (Surface Manager), 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), clipboard service module (ClipboardService), media scanning service module (MediaScannerService), media database (Media Database), etc.

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

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

A 2D graphics engine is a drawing engine for 2D drawings.

The clipboard service module can be used to provide clipboard related services. For example, the clipboard service module can obtain and save the shared data (such as screenshot images, etc.) in the shared data storage module; for another example, the clipboard service module can determine whether the shared data in the shared data storage module obtained is a picture (such as a screenshot image, etc.); for another example, the clipboard service module can notify the following media scanning service module to scan the path of the shared data in the shared data storage module when it is determined that the shared data in the shared data storage module obtained is a picture; and so on. It is easy to understand that saving data in the clipboard service module can be considered as saving the data in the clipboard.

The media scanning service module can be used to scan media files. For example, the media scanning service module can receive an instruction message sent by the clipboard service module, and based on the instruction message, scan the path of the shared data in the shared data storage module, and insert the information of the shared data that meets the preset rules (such as the preset screenshot rules) into the following media database.

The media database can be used to store information about media files, for example, information about the shared data that complies with preset rules.

The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, Bluetooth driver, and sensor driver.

In an embodiment of the present application, the kernel layer may also include a shared data storage module and an inter-process communication module.

The shared data storage module can be used to store shared data (i.e., data that both the host operating system and the client operating system have access to). For example, the shared data storage module can receive and store information about shared data synchronized from the shared data storage module in the host operating system. It is easy to understand that all files in the "shared folder" in the aforementioned embodiment can be stored in the shared data storage module.

The inter-process communication module can be used to implement the function of communication between two processes. For example, the inter-process communication module can receive an IPC message sent by the host operating system, and can also send the IPC message to the clipboard service module.

Based on the software structure of Figures 5 and 6 above, the following introduces a possible collaboration method between various modules when the electronic device 100 implements the screenshot sharing method provided in an embodiment of the present application when a host operating system is installed and a client operating system is loaded on the host operating system.

FIG. 7 exemplarily shows a possible collaboration mode between various modules when the electronic device 100 implements the screenshot sharing method provided in an embodiment of the present application when a host operating system is installed and a client operating system is loaded on the host operating system.

When step S403 in FIG. 4 is executed, a possible collaboration mode between the modules of the electronic device 100 may be the collaboration mode shown in the following steps 1 and 2:

Step 1-Step 2: After the screenshot application generates the screenshot image 1, the screenshot application can send the information of the screenshot image 1 to the clipboard service module of the host operating system by calling the clipboard management module of the host operating system, and the clipboard service module of the host operating system can save the information of the screenshot image 1.

When steps S404-S405 in FIG. 4 are executed, a possible collaboration mode between the modules of the electronic device 100 may be the collaboration mode shown in the following steps 3-4:

Step 3: The clipboard service module of the host operating system can determine whether the screenshot image 1 is a picture. If so, the information of the screenshot image 1 is sent to the shared data storage module of the host operating system, and the shared data storage module of the host operating system can save the information of the screenshot image 1.

Step 4: The shared data storage module of the host operating system may synchronize the information of the screenshot image 1 to the shared data storage module of the client operating system, and the shared data storage module of the client operating system may save the information of the screenshot image 1 .

In the embodiment of the present application, a shared data storage module may exist in both the host operating system and the client operating system. In some examples, the shared data storage module may exist only in the host operating system but not in the client operating system. In this case, the client operating system needs to obtain the information of the screenshot image 1 from the shared data storage module of the host operating system. In other examples, the shared data storage module may exist only in the client operating system but not in the host operating system. In this case, after generating the screenshot image 1, the host operating system may save the information of the screenshot image 1 to the shared data storage module of the client operating system. After that, the client operating system may directly obtain the information of the screenshot image 1 from the shared data storage module of the client operating system.

When step S406 in FIG. 4 is executed, a possible collaboration mode between the modules of the electronic device 100 may be the collaboration mode shown in the following steps 5 to 8:

Step 5: The clipboard listening module of the host operating system monitors in real time whether the content stored in the clipboard service module of the host operating system changes.

It is easy to understand that step 5 can be executed simultaneously when the above steps 1 to 4 are executed.

Step 6-Step 8: When the clipboard listening module of the host operating system detects that the content saved in the clipboard service module of the host operating system has changed, the clipboard listening module of the host operating system can send an IPC message to the clipboard service module of the client operating system through the inter-process communication module of the host operating system and the inter-process communication module of the client operating system. The message can be used to instruct the clipboard service module of the client operating system to obtain the information of the screenshot image 1.

When steps S407-S408 in FIG. 4 are executed, a possible collaboration mode between the modules of the electronic device 100 may be the collaboration mode shown in step 9 below:

Step 9: The clipboard service module of the client operating system obtains the information of the screenshot image 1 from the shared data storage module of the client operating system, and saves the information of the screenshot image 1.

It is easy to understand that after the clipboard service module of the client operating system saves the information of the screenshot image 1, the screenshot image 1 will exist in the clipboard of the client operating system.

When steps S409-S410 in FIG. 4 are executed, a possible collaboration mode between the modules of the electronic device 100 may be the collaboration mode shown in the following steps 10-12:

Step 10-Step 12: The clipboard service module of the client operating system can determine whether the above-mentioned screenshot image 1 is a picture. If so, it can notify the media scanning service module of the client operating system to scan the path corresponding to the information of the screenshot image 1 in the shared data storage module of the client operating system. If the media scanning service module of the client operating system determines through the scanning operation that the information of the above-mentioned screenshot image 1 meets the preset rules, the information of the above-mentioned screenshot image 1 can be inserted into the media database of the client operating system.

When steps S412-S413 in FIG. 4 are executed, a possible collaboration mode between the modules of the electronic device 100 may be the collaboration mode shown in the following steps 13-15:

Step 13: The chat application (ie, an application with social functions) of the client operating system can monitor in real time whether the content in the media database changes.

In some examples, the chat application of the client operating system may not monitor the content in the media database for changes in real time, but may monitor the content in the media database for changes under certain conditions, such as when the chat application is opened, or when the chat interface of the chat application is triggered to be displayed.

Step 14-Step 15: When the chat application of the client operating system detects changes in the content in the media database of the host operating system, an automatic sharing action can be triggered, for example, a floating window 261 is displayed in the user interface 260 in Figure 2D. Furthermore, the chat application of the client operating system can obtain the information of the screenshot image 1 saved in the clipboard service module of the client operating system by calling the clipboard management module of the client operating system, and display the screenshot image 1 in the above-mentioned floating window 261 based on the information of the screenshot image 1.

The structure of an electronic device 100 provided in an embodiment of the present application is introduced below.

FIG. 8 exemplarily shows the structure of an electronic device 100 provided in an embodiment of the present application.

As shown in FIG8 , the electronic device 100 may include a processor 110, an internal memory 120, an external memory interface 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, a display screen 151, a keyboard 152, a camera 153, an audio module 160, a speaker 161, a receiver 162, a microphone 163, an earphone interface 164, a wired communication module 171, a wireless communication module 172, an antenna 1, a sensor module 180, etc. The sensor module 180 may include a pressure sensor 180A, a fingerprint sensor 180B, a temperature sensor 180C, a touch sensor 180D, an ambient light sensor 180E, etc.

It is understandable that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other examples of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. For example, in some examples, in addition to the hardware described above, the electronic device 100 may also have a motor, a mobile communication module (2G/3G/4G/5G), a SIM card interface, an eSIM chip, and the like. Therefore, regarding the specific hardware structure of the electronic device 100, it may include more or fewer components than shown in the figure, or Combine some parts, or split some parts, or arrange the parts differently.

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 processor (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), etc. Different processing units may be independent devices or integrated in one or more processors.

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.

The processor 110 may also be provided with a memory for storing instructions and data. In some examples, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

In some examples, processor 110 may include one or more interfaces. The interface 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, etc.

The USB interface 130 is an interface that complies with USB standard specifications, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 may be used to connect a charger to charge the electronic device 100, or may be used to transmit data between the electronic device 100 and a peripheral device. The interface may also be used to connect other electronic devices, such as AR devices, etc.

It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other examples of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The internal memory 120 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 120. The internal memory 120 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, etc. In addition, the internal memory 120 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.

The external memory interface 121 can be used to connect an external memory card, such as a mobile hard disk, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 121 to implement a data storage function, such as storing music, video and other files in an external storage hard disk.

The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging examples, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging examples, the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 120, the external memory, the display screen 151, the camera 153, and the wireless communication module 172. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other examples, the power management module 141 can also be set in the processor 110. In other examples, the power management module 141 and the charging management module 140 can also be set in the same device.

The electronic device 100 implements the display function through a GPU, a display screen 151, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 151 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 151 is used to display images, videos, etc. The display screen 151 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light emitting diode or an active-matrix organic light emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light emitting diode (quantum dot light emitting diode), or a micro-LED. In some embodiments, the electronic device 100 may include 1 or N display screens 151, where N is a positive integer greater than 1.

The keyboard 152 may include a physical keyboard, a touch keyboard, etc. The electronic device 100 may receive input from the keyboard and generate key signal input related to user settings and function control of the electronic device 100. For example, the user may use shortcut keys on the keyboard 152 to perform operations such as taking screenshots and pasting screenshot images.

The electronic device 100 can realize the shooting function through the ISP, the camera 153, the video codec, the GPU, the display screen 151 and the application processor.

The camera 153 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 153, where N is a positive integer greater than 1.

The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

Video codecs are used to compress or decompress digital videos. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record videos in a variety of coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

The network communication function of the electronic device 100 can be implemented through the wired communication module 171, the wireless communication module 172, the antenna 1, the modem processor and the baseband processor. Through the network communication function of the electronic device 100, the electronic device 100 can communicate with other electronic devices, for example, to share screenshots with other electronic devices (such as a friend's electronic device).

Antenna 1 is 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 the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other examples, the antenna can be used in combination with a tuning switch.

The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 161, a receiver 162, etc.), or displays an image or video through a display screen 151. In some embodiments, the modem processor may be an independent device.

The wired communication module 171 can provide wired communication solutions including Ethernet, local area network, Internet, etc. applied to the electronic device 100. The wired communication module 171 can be one or more devices integrating at least one communication processing module.

The wireless communication module 172 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) and the like applied to the electronic device 100. The wireless communication module 172 can be one or more devices integrating at least one communication processing module. The wireless communication module 172 receives electromagnetic waves via the antenna 1, modulates the frequency of the electromagnetic wave signal and performs filtering processing, and sends the processed signal to the processor 110. The wireless communication module 172 can also receive the signal to be sent from the processor 110, modulate the frequency of the signal, amplify the signal, and convert it into electromagnetic waves for radiation through the antenna 1.

The electronic device 100 can implement audio functions such as music playing and recording through the audio module 160 , the speaker 161 , the receiver 162 , the microphone 163 , the headphone jack 164 , and the application processor.

The audio module 160 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 160 can also be used to encode and decode audio signals. In some embodiments, the audio module 160 can be arranged in the processor 110, or some functional modules of the audio module 160 can be arranged in the processor 110.

The speaker 161 , also called a “speaker”, is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 161 .

The receiver 162, also called a "handset", is used to convert audio electrical signals into sound signals. When the user is listening to the voice, the user can place the receiver 162 close to the ear.

Microphone 163, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting his mouth close to microphone 163 to input the sound signal into microphone 163. The electronic device 100 can be provided with at least one microphone 163. In other examples, the electronic device 100 can be provided with two microphones 163, which can not only collect sound signals but also realize noise reduction function. In other examples, the electronic device 100 can also be provided with three, four or more microphones 163 to collect sound signals, reduce noise, identify the sound source, realize directional recording function, etc.

The earphone jack 164 is used to connect a wired earphone. The earphone jack 164 can be the USB interface 130, or a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

The sensor module 180 may include a pressure sensor 180A, a fingerprint sensor 180B, a temperature sensor 180C, a touch sensor 180D, an ambient light sensor 180E, and the like.

The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some examples, the pressure sensor 180A can be set on the display screen 151. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, 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 151, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 can also calculate the position of the touch based on the detection signal of the pressure sensor 180A. In some examples, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions.

The fingerprint sensor 180B is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

The temperature sensor 180C is used to detect temperature. In some examples, the electronic device 100 uses the temperature detected by the temperature sensor 180C to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180C exceeds a threshold, the electronic device 100 reduces the performance of a processor located near the temperature sensor 180C to reduce power consumption and implement thermal protection. In other examples, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 due to low temperature. In other examples, when the temperature is lower than another threshold, the electronic device 100 performs a boost on the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

The touch sensor 180D is also called a "touch panel". The touch sensor 180D is used to detect a touch operation applied thereto or thereabout. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. A visual output related to the touch operation can be provided through the display screen 151.

The ambient light sensor 180E is used to sense the brightness of the ambient light. The electronic device 100 can adaptively adjust the brightness of the display screen 151 according to the perceived brightness of the ambient light. The ambient light sensor 180E can also be used to automatically adjust the white balance when the camera 153 is shooting.

It should be understood that the electronic device 100 shown in FIG8 is only an example, and the electronic device 100 may have more or fewer components than those shown in FIG8, may combine two or more components, or may have a different component configuration. The various components shown in FIG8 may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.

A person skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by a computer program to instruct the relevant hardware, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned method embodiments. The aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk, etc. The medium of the code.

The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

A screenshot sharing method is applied to an electronic device, wherein a first operating system and a second operating system are running on the electronic device, and the method comprises:

In response to a screenshot operation by the user, the first operating system generates and saves a screenshot image;

The second operating system obtains the screenshot image, and saves the screenshot image to a clipboard of the second operating system;

The second operating system displays a floating window in a user interface, the floating window is generated based on the screenshot image, and the user interface is a user interface of an application in the second operating system;

The second operating system detects a first operation of a user on the floating window on the user interface;

In response to the first operation, the electronic device sends the screenshot image to other devices.
The method according to claim 1, characterized in that before the second operating system obtains the screenshot image, the method further comprises:

The first operating system sends a first message to the second operating system, where the first message is used to instruct the second operating system to obtain the screenshot image.
The method according to claim 2 is characterized in that the first message is sent via inter-process communication (IPC).
The method according to any one of claims 1 to 3, wherein the first operating system saves the screenshot image, comprising:

The first operating system saves the screenshot image to a clipboard of the first operating system and to a shared folder.
The method according to claim 4, characterized in that before the first operating system sends the first message to the second operating system, the method further comprises:

The first operating system detects that the most recently saved content in the clipboard of the first operating system is a picture.
The method according to claim 4 or 5, characterized in that the second operating system obtains the screenshot image, comprising:

The second operating system obtains the screenshot image from the shared folder.
The method according to any one of claims 4 to 6, characterized in that before the second operating system displays the floating window in the user interface, the method further comprises:

The second operating system scans the path of the screenshot image in the shared folder, and inserts information of the screenshot image into a media database based on the path.
The method according to claim 7, characterized in that the second operating system inserts the information of the screenshot image into the media database based on the path, comprising:

The second operating system inserts information of the screenshot image into a media database when determining, based on the path, that the screenshot image meets a preset rule;

Among them, the preset rules include any one or more of the following: the naming of the screenshot image includes specific keywords, the time interval between the time point recorded in the timestamp information of the screenshot image and the first time point is within a preset time interval, and the first time point is the time point when the second operating system scans the path of the screenshot image in the shared folder.
The method according to claim 7 or 8, characterized in that after the second operating system inserts the information of the screenshot image into the media database based on the path, the method further comprises:

The application program obtains the screenshot image from the clipboard of the second operating system.
The method according to any one of claims 1 to 9 is characterized in that the screenshot operation includes one or more of the following: an operation of selecting a screenshot area, and an editing operation on the screenshot area.
An electronic device, characterized in that the electronic device comprises one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, the one or more memories are used to store computer program codes, and the computer program codes include computer instructions, and when the one or more processors execute the computer instructions, the electronic device executes the method as described in any one of claims 1-10.
A computer storage medium, characterized in that the computer storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed on an electronic device, the electronic device executes the method as described in any one of claims 1 to 10.