An information processing method, computer program product and electronic device

Abstract

The present disclosure provides an information processing method, which comprises: in response to a preset touch operation on a target interface element in a graphical user interface, displaying an enlarged area at the position of the target interface element, and displaying the target interface element in the enlarged area in an enlarged manner; and in response to a movement operation on the enlarged area, moving the enlarged area on the graphical user interface, and updating the display of the target interface element in the enlarged area according to the position covered by the enlarged area. Through the method provided by the present disclosure, the user of a software application such as a game application can quickly summon a movable magnifying glass at any interface position of interest through a simple gesture, and the magnifying operation is liberated from cumbersome global settings or fixed areas, realizing the precise and convenient interactive experience of "looking where you point", and significantly improving the friendliness and efficiency of human-computer interaction.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to an information processing method, computer program product, and electronic device. Background Technology

[0002] In various software applications, especially mobile games, particularly those with dense interface elements and complex operations, such as MMOs (Massively Multiplayer Online Role-Playing Games), players typically need to explore a vast virtual world, complete quests, interact with other players, and frequently interact with numerous function buttons, small text messages, and icons on the interface. To improve the visual experience on mobile devices, some games offer interface scaling features. For example, players can access the game settings menu and adjust the global interface scaling ratio to enlarge all text, icons, and other elements by a fixed proportion. However, these solutions have several drawbacks in practical applications, impacting both experience and efficiency. First, the global scaling or settings adjustment method involves a lengthy operation path, which becomes particularly cumbersome during fast-paced gameplay, disrupting player immersion. Second, a uniform scaling ratio can cause interface layout distortion, with some important information being obscured by enlarged elements, limiting the possibility of players exploring complex gameplay and performing precise operations. Finally, from a technical implementation perspective, real-time scaling and rendering of the entire interface or a large area will significantly increase the graphics processing burden and power consumption of mobile terminals, and may also generate more data interaction needs, thereby squeezing out limited device storage and server resources. Summary of the Invention

[0003] This disclosure provides an information processing method, computer program product, and electronic device to at least partially solve the aforementioned problems in the related technologies, thereby enabling convenient gesture-triggered local magnification and intelligent assistance functions, and improving the operation and viewing experience of older users in mobile games and other software applications.

[0004] According to a first aspect of this disclosure, an information processing method is provided, comprising: in response to a preset touch operation on a target interface element in a graphical user interface, displaying a magnified area at the location of the target interface element, and magnifying the target interface element in the magnified area; in response to a movement operation on the magnified area, moving the magnified area on the graphical user interface, and updating the display of the target interface element in the magnified area according to the position covered by the magnified area.

[0005] According to a second aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the method of the first aspect described above and its possible implementations.

[0006] According to a third aspect of this disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the method of the first aspect and possible implementations thereof by executing the executable instructions.

[0007] This disclosure provides an information processing method that, in response to a preset touch operation on a target interface element in a graphical user interface, displays a magnified area at the location of the target interface element and magnifies the target interface element within the magnified area; in response to a movement operation on the magnified area, moves the magnified area on the graphical user interface and updates the display of the target interface element within the magnified area according to the position covered by the magnified area. The method disclosed herein enables users of software applications such as games to quickly summon a movable magnifying glass at any desired interface location using simple gestures. Addressing the core pain point of older users experiencing "unable to see clearly or click" due to declining eyesight, this method liberates magnification from cumbersome global settings or fixed areas, achieving a precise and convenient "point-and-see" interactive experience, significantly improving the friendliness and efficiency of human-computer interaction. Simultaneously, because the magnified area is localized and movable, users can freely explore every detail of the graphical user interface (GUI) such as game interfaces without worrying about disrupting the interface layout. This encourages users to participate more deeply in the complex systems and intricate functions of software applications, indirectly improving the usability and richness of the applications. Furthermore, this solution renders and magnifies only a localized area when needed, significantly reducing the real-time computing load and memory consumption of the graphics processing unit (GPU) compared to related technologies that rescale the entire interface or a large area. This optimizes the resource utilization efficiency of mobile devices, representing a typical solution to a computer technology problem of improving software interaction performance under limited hardware resources. Attached Figure Description

[0008] Figure 1 A schematic diagram of a system architecture is shown in one exemplary embodiment of this disclosure;

[0009] Figure 2 A flowchart illustrating an information processing method in one exemplary embodiment of this disclosure is shown; Figure 3a A schematic diagram of a graphical user interface in one exemplary embodiment of the present disclosure is shown; Figure 3b A schematic diagram of a graphical user interface in one exemplary embodiment of the present disclosure is shown; Figure 4a A schematic diagram of a graphical user interface in one exemplary embodiment of the present disclosure is shown; Figure 4bA schematic diagram of a graphical user interface in one exemplary embodiment of the present disclosure is shown; Figure 5a A schematic diagram of a graphical user interface in one exemplary embodiment of the present disclosure is shown; Figure 5b A schematic diagram of a graphical user interface in one exemplary embodiment of the present disclosure is shown; Figure 6 A schematic diagram of the structure of an electronic device is shown in one exemplary embodiment of the present disclosure. Detailed Implementation

[0010] Exemplary embodiments of this disclosure will be described more fully below with reference to the accompanying drawings.

[0011] To enable those skilled in the art to better understand the present disclosure, the technical solutions of the present disclosure will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of the present disclosure, and not all embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present disclosure.

[0012] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0013] The accompanying drawings are schematic illustrations of this disclosure and are not necessarily drawn to scale. Some block diagrams shown in the drawings may be functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in hardware modules or integrated circuits, or in networks, processors, or microcontrollers. Implementations can be carried out in various forms and should not be construed as limited to the examples set forth herein. The features, structures, or characteristics described in this disclosure can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough description of embodiments of this disclosure. However, those skilled in the art will recognize that one or more specific details may be omitted when implementing the technical solutions of this disclosure, or other methods, components, apparatuses, steps, etc., may be used to replace one or more specific details.

[0014] Figure 1 A system architecture diagram of the operating environment of this exemplary embodiment is shown. This system architecture may include a terminal device 110 and a server 120. The terminal device 110 may be a mobile phone, tablet computer, personal computer, smart wearable device, game console, etc., and has a display function capable of displaying a graphical user interface, which may include the operating system interface or the application interface. An application, such as a game program, is installed on the terminal device 110. The server 120 generally refers to the backend system providing the game service in this exemplary embodiment; it may be a single server or a cluster of multiple servers. For example, a game server program is deployed on the server 120 to perform server-side game data processing. The terminal device 110 and the server 120 can be connected via a wired or wireless communication link for data transmission. The method in one exemplary embodiment of this disclosure can be executed by any one or more of the terminal device 110 and the server 120.

[0015] In one implementation, the above method can be implemented and executed based on a cloud interaction system. The cloud interaction system can be the system architecture described above. Various cloud applications, such as cloud gaming, can run under the cloud interaction system. Taking cloud gaming as an example, cloud gaming can be a game mode based on cloud computing. In the cloud gaming operation mode, the game program's execution entity and the game screen presentation entity are separated. The storage and execution of the game's control and interaction methods are completed on the cloud gaming server (such as the aforementioned server 120). The cloud gaming client (such as the aforementioned terminal device 110) is responsible for receiving and sending data and presenting the game screen. For example, the cloud gaming client can be a display device with data transmission capabilities located close to the user, such as a mobile terminal, television, computer, or PDA; while the cloud gaming server in the cloud performs information processing. When playing the game, the user operates the cloud gaming client to send operation commands to the cloud gaming server. The cloud gaming server runs the game according to the operation commands, encodes and compresses the game screen and other data, returns it to the cloud gaming client via the network, and finally, the cloud gaming client decodes and outputs the game screen.

[0016] In one implementation, the method described above can be implemented by the terminal device 110 alone. For example, without deploying the server 120, the terminal device 110 can run the application in a standalone environment to implement the game function and execute the method described above.

[0017] According to one embodiment of this disclosure, an information processing method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0018] An information processing method according to one embodiment of this disclosure, such as Figure 2 As shown, the method may include the following steps: Step S210: In response to a preset touch operation on a target interface element in the graphical user interface, a magnified area is displayed at the location of the target interface element, and the target interface element is magnified and displayed in the magnified area.

[0019] In step S230, in response to the operation of moving the zoomed-in area, the zoomed-in area is moved on the graphical user interface, and the target interface element in the zoomed-in area is updated according to the position covered by the zoomed-in area.

[0020] The method provided in this embodiment enables users to quickly and accurately locate and view magnified interface details by performing a preset touch operation on the target interface element, thereby reducing searching and accidental operations and improving the directness and convenience of interaction. By supporting free movement of the magnified area and real-time updates of its internal display content, users can explore magnified details of different parts of the interface without leaving the current context, increasing the flexibility and freedom of interface browsing and content exploration, thus enhancing the richness of the application. This method captures specific touch events programmatically, dynamically generates and associates a movable magnified display layer, and remaps and renders interface elements based on the real-time position coordinates of this layer, solving the computer display and interaction technology problem of how to efficiently and dynamically provide local magnification viewing functionality on small screens or high-density interfaces.

[0021] The steps described above are explained in detail below.

[0022] In step S210, in response to a preset touch operation on a target interface element in the graphical user interface, a magnified area is displayed at the location of the target interface element, and the target interface element is magnified and displayed in the magnified area.

[0023] Interface elements are visually recognizable components in a graphical user interface, such as icons, text, controls, or buttons; target interface elements are the specific objects the user wants to zoom in on. Preset touch operations are predefined gesture inputs, such as long press, hard press, circle drawing, or double-tap; these preset touch operations serve as trigger conditions for activating the zoom-in display mode. The zoom-in area can be an independent display layer overlaid on the original interface, such as a circular, rectangular, elliptical, or other shaped display window; the zoom-in area is used to hold and display the zoomed-in target interface element content.

[0024] In step S230, in response to the operation of moving the zoomed-in area, the zoomed-in area is moved on the graphical user interface, and the target interface element in the zoomed-in area is updated according to the position covered by the zoomed-in area.

[0025] Among them, the movement operation is a touch operation that acts on the magnified area itself, such as dragging or sliding by pressing and holding a single finger on the magnified area itself, its boundary, or a specific movement control on the boundary. The movement operation is used to change the display position of the magnified area on the screen. As the position of the magnified area on the graphical user interface changes, the magnified target interface elements displayed in the magnified area also change accordingly. That is, the magnified area displays the magnified display effect of the interface elements currently covered by the magnified area in real time.

[0026] In one specific application of this embodiment, as shown in the appendix to the specification... Figure 3aAs shown, when a user is viewing the graphical user interface of a game application on an electronic device (especially a mobile electronic device), and finds that an interface element 301 (such as the text in the attached diagram) is difficult to identify, the user can perform a circular gesture on the target interface element through the electronic device (for example, using a mouse peripheral to control the mouse icon on the graphical user interface to draw a circle around the target interface element, or using a finger to draw a circle around the target interface element on the touch screen). The system will immediately display a circular magnifying glass window 302 at the target interface element (as shown in the instruction manual). Figure 3b As shown in the image, the magnified interface element 303 is clearly displayed. Next, the user can drag this magnifying glass window with the mouse or finger to other interface elements that need to be magnified (as shown in the instruction manual). Figure 4a As shown, the zoomed-in area 401 before moving displays the zoomed-in interface element 402, which is the part of the game activity description text. After the magnifying glass window is moved to the new position (the position of the interface element 403 before zooming in, which is the position of the "Redeem Rewards" control), the content displayed inside it is also updated to the zoomed-in view of the currently covered position (as shown in the instruction manual). Figure 4b As shown, the content displayed in the magnified area 401 is updated to the magnified interface elements 404 and 405, thus making it easier for users to continuously view the details of different areas of the interface.

[0027] In an optional implementation, in response to a target interface element covered by the zoomed-in area containing a prompt message, the prompt message is displayed outside the zoomed-in area. Thus, when a user uses the zoom function to view interface details, if the viewed element has a prompt message, this message can be clearly presented outside the zoomed-in area. This eliminates the need for a separate step to trigger the display of the prompt message on the target interface element, and also prevents key prompts from being obscured by the zoomed-in view itself. This ensures that the user can simultaneously obtain the zoomed-in details and related auxiliary explanations, thereby optimizing the completeness of information browsing and operational efficiency.

[0028] For example, as shown in the instruction manual Figure 4b As shown, the user moves the circular magnified area 401 to the location of the "Redeem Reward" control. At this point, the magnified area 401 displays magnified control-type interface elements 405 and magnified text-type interface elements 404. Because the "Redeem Reward" control contains a prompt (the specific time to redeem the reward), this prompt information 406 is displayed in clear and legible font on the right side of the magnified area 401. The magnified interface element 404, however, corresponds to plain text interface information and does not contain any prompt information. This allows the user to see both the magnified interface elements and effortlessly read the complete description of those elements without worrying that the magnifying glass window will obscure this important explanatory text.

[0029] Optionally, tooltips refer to auxiliary content associated with target interface elements, used to provide users with additional explanations, annotations, warnings, or operational guidance. They can take many forms, such as tooltips that appear when the mouse cursor hovers over a button (the most common form); prompts that pop up after a user clicks an icon in the graphical user interface; red badges or numbers displayed in the corner of icons to indicate the number of unread messages or update status; or error messages attached to input boxes to provide correction suggestions when user input is not formatted correctly. These tooltips are usually text-based, but may also include simple icons or animations. Their core function is to supplement information not directly conveyed by the main interface elements, lowering the barrier to understanding and operation for users. The identified tooltips need to be displayed appropriately to avoid visual conflict or obstruction with the main content within the magnified area; therefore, displaying them outside the magnified area is a logical choice. This approach considers that the core visual focus of users viewing magnified content is usually located in the center of the magnified area. Placing supplementary information on the periphery ensures uninterrupted viewing of the main content while allowing auxiliary information to easily enter the user's field of vision when needed.

[0030] Optionally, the condition that the target interface element covered by the zoomed-in area contains a prompt message describes the specific triggering scenario for the system's judgment and response. This involves two levels of judgment: first, a spatial relationship judgment, i.e., whether the current display area of ​​the zoomed-in area overlaps with the display area of ​​the target interface element on the screen. Generally, as long as the bounding box of the zoomed-in area intersects with the bounding box of the interface element, or the center point of the zoomed-in area falls within the display area of ​​the interface element, it can be considered a cover. Second, a content attribute judgment, i.e., whether the covered target interface element is logically associated with a prompt message. This association may be statically bound, such as a settings button that always has a "Click to enter the settings menu" prompt; or it may be dynamically generated, such as a chart displaying real-time data, whose prompt message might be the specific value of the current data point, which changes over time. The system needs to perform such cover detection and content analysis every frame or every time the zoomed-in area position is updated. When the user moves the zoomed-in area over these icons, the system needs to calculate the positional relationship between the zoomed-in area and each icon in real time. Once cover occurs, it further checks whether the covered icon has any additional information attributes besides the filename. If this is detected, subsequent display logic is triggered. This mechanism allows the system to intelligently perceive the context and only display additional information when there is truly additional information available, thus avoiding redundancy and clutter in the interface elements.

[0031] Optionally, the step of displaying the prompt outside the magnified area defines the specific location and method of information presentation, with the core principle being supplementation rather than interference. The display location can be dynamically calculated using various strategies. A common strategy is to display the prompt in an area immediately adjacent to the magnified area, such as right next to the top, bottom, left, or right edges. The specific location can be chosen based on remaining screen space and aesthetic principles, prioritizing placement on the side with more available space. Another strategy is to display the prompt in a relatively fixed auxiliary information area on the screen, such as the status bar or sidebar at the top or bottom of the screen, and visually indicate its connection to the currently magnified target interface element through lines or highlighting. The display style also needs to be adapted. When the prompt is displayed outside the magnified area, its font size, color, and background may need to be adjusted to ensure sufficient readability against the original interface background while maintaining consistency with the overall interface design style. For example, the original floating tooltip might be small white text on a semi-transparent black background. When displayed outside the zoomed-in area, it might need to dynamically adjust the text color and background contrast based on the actual background color of the area surrounding the zoomed-in region, or even add a slight shadow or outline to enhance readability. Furthermore, the display process could be a fade-in / fade-out animation to smoothly attract the user's attention, rather than abruptly popping up. If the user continues to move the zoomed-in area, covering another element containing different tooltip information, the externally displayed tooltip content needs to be updated in real time, creating a dynamic following effect. This external display mechanism essentially creates a secondary view outside the main zoomed-in view, dedicated to displaying related metadata; the two are spatially separate but logically tightly coupled.

[0032] In an optional implementation, in response to the target interface element covered by the magnified area containing a functional control, a magnified control of the functional control is displayed outside the magnified area; in response to a touch operation on the magnified control, the function of the corresponding functional control is executed. Thus, when a user views the interface through the magnified area, if it covers a functional control that was originally smaller or densely packed, a larger, more easily identifiable and operable copy of the control can be provided outside the magnified area. The user can directly perform a touch operation on the magnified control to trigger the function, avoiding the problems of accidental touches or insufficient operation precision that are easily caused when operating on the original small-sized control, improving the success rate of operation and interaction efficiency, and enhancing the user's experience of calling functions when viewing partially magnified content.

[0033] For example, as shown in the instruction manual Figure 4bAs shown, the user moves the circular magnified area 401 to the location of the "Redeem Rewards" control. Since the system recognizes that the "Redeem Rewards" control is a functional control that can trigger the corresponding function (i.e., redeeming corresponding game rewards based on the player's current activity points), the system immediately generates a magnified control 407, which is larger than the original control, in the lower right corner of the external graphical user interface of the magnified area 401. After seeing this magnified control 407, the user can directly click on this larger button copy. The system then responds to the click operation and executes the same reward redemption function as the original control, so that the user can complete the operation without having to aim at the original small button.

[0034] Optionally, functional controls are interactive interface elements in a graphical user interface (GUI) designed to receive user input commands and trigger the software to execute one or more predefined functions or operations. These controls typically have specific visual representations, such as buttons, switches, sliders, icons, or menu items, and are associated with background program logic. From an interaction perspective, functional controls differ from static display elements in that they possess an event response mechanism, capable of responding to user input events such as touch, click, long press, and drag. In interface layouts, functional controls can appear in various application scenarios, such as toolbars, dialog boxes, sidebars, or main content areas. Their functionality is broad, potentially including submitting form data, adjusting system parameters, navigating to other pages, playing media content, or launching specific tools. When a zoomed-in area covers the interface, the system needs to identify the interface elements within the zoomed-in area's visual range and determine which of them are functional controls. This determination can be based on the control's type label, whether it is bound to an event listener, or its interaction attribute identifier. For example, in a form containing text labels and a submit button, the submit button will be identified as a functional control, while the plain text label will not. Identifying functional controls is the foundation for subsequent zoom-in display and interaction.

[0035] Optionally, a magnifying control is a visually enlarged copy of the original functional control, displayed outside the magnified area. This magnifying control is functionally equivalent to its original functional control, meaning they are associated with the same program instructions or operation sequences. From a visual perspective, magnifying controls typically retain the basic style, color, icon, or text label of the original control, but their size is significantly increased to improve readability and operability. Their display position is not arbitrary but related to the magnified area; a common strategy is to display them near the outer edge of the magnified area, such as above, below, left, right, or in the four corners, to avoid obscuring the main content view within the magnified area. The generation of the magnifying control can be dynamic, created and rendered in real-time when the system detects that the magnified area covers the functional control; its display state can also be linked to the movement of the magnified area in real-time, disappearing when the magnified area moves away and no longer covers the functional control. In some implementations, the magnifying control may not only be enlarged in size but may also have subtle visual enhancements, such as more pronounced shadows or borders, to further emphasize its interactivity. It acts as a proxy or bridge for users to interact with the original small-sized controls, solving the physical difficulties of interacting with tiny controls in zoom-in viewing mode.

[0036] In an optional implementation, if the target interface element covered by the magnified area contains multiple functional controls, displaying magnified versions of these functional controls outside the magnified area includes: centrally displaying magnified versions of multiple functional controls outside the magnified area. In this way, when the magnified area simultaneously covers multiple dense or small functional controls, the system can centrally display magnified versions of these controls in one area, rather than scattering them across the screen. This allows users to quickly locate the large-sized operation entry point for the desired function when zooming in to view content, avoiding visual jumps and operational inconvenience caused by the dispersed positions of multiple magnified controls, effectively improving operational convenience and interaction efficiency in multi-control scenarios.

[0037] For example, in the interface of a graphic design application, when a user moves a circular zoom-in area over a toolbar containing multiple tiny tool icons (such as a brush, eraser, and fill bucket), since the area simultaneously covers more than one functional control, the system will generate a rectangular centralized display panel on one side of the zoom-in area, such as the right side. This panel neatly arranges enlarged buttons corresponding to the icons in the original toolbar. The user does not need to precisely remember the position of the original icons; they only need to find and click the corresponding large brush button in the centralized panel to select the brush tool. This enables efficient access and retrieval of multiple compact functions in a local zoom-in viewing mode.

[0038] Optionally, centralized display refers to a visual layout where multiple independent magnifying controls are arranged and presented as a collection in adjacent positions on the screen. Its core purpose is to integrate multiple magnifying controls that might have been scattered due to their original locations into a relatively compact and orderly visual unit, thus providing the user with a unified and centralized entry point. In terms of presentation, the centralized display area typically has a clear visual boundary or background area, such as a semi-transparent rectangular panel, a shadowed overlay, or a container of a specific shape, used to visually aggregate the multiple magnifying controls within it, distinguishing it from the rest of the interface. The internal layout of this area follows certain arrangement rules. Common arrangements include horizontal linear arrangement, vertical linear arrangement, grid arrangement, or circular arrangement, depending on the number and shape of the magnifying controls and the available screen space. For example, three magnifying controls can be displayed horizontally side-by-side; for six or more controls, a two-row, three-column grid arrangement may be used. Centralized display not only focuses on spatial clustering but also emphasizes the visual order between controls, ensuring appropriate spacing between adjacent controls to avoid overlapping or obstruction, and maintaining neatness in the arrangement, such as alignment with a common baseline or center line. This layout eliminates the need for users to search for individual zoom controls in different corners of the screen; instead, they can expect all available zoom functions to be located within a specific, easily locatable area.

[0039] In an optional implementation, the zoomed-in area covering the interface element includes: the center of the zoomed-in area at least partially overlapping the position of the target interface element. This provides a clear and easily calculated spatial relationship determination criterion by using the geometric center of the zoomed-in area as a reference point to determine whether an interface element is covered. When the center point of the zoomed-in area (such as a circular area) falls within or touches the boundary of the target interface element, the coverage logic is triggered. This determination method reduces ambiguity caused by blurred boundaries or partial coverage, ensuring the accuracy and consistency of the zoom function triggering. It allows users to more accurately control the target they want to view or operate by moving the center of the zoomed-in area, improving the intuitiveness and controllability of the interaction.

[0040] For example, in a chart analysis application containing dense data points, a user uses a circular magnifying glass tool to view the detailed numerical label of a specific data point. As the user moves the circular magnifying area, the system continuously detects whether the screen coordinates of the circle's center point intersect with the rectangular pixel area occupied by a data point icon. Once the center of the magnifying area moves to coincide with the edge or inner area of ​​a data point icon, even if the edge of the circle does not completely surround the icon, the system will immediately determine that the data point icon is the target interface element and magnify and display the icon and its accompanying detailed numerical information within the magnifying area, thereby achieving accurate target positioning based on center point overlap.

[0041] Optionally, the center position of the magnified area is a key geometric reference point used for spatial calculations and relationship determination. Its specific meaning depends on the shape and definition of the magnified area. For magnified areas with regular geometric shapes, the center position typically corresponds to the geometric center of that shape in mathematical definition. For example, if the magnified area is defined as a circle, its center position is the center of the circle, which can be determined by the center of the circle's circumscribed rectangle or directly defined center coordinates. If the magnified area is a rectangle, its center position is the intersection of the rectangle's two diagonals, or the point determined by the midpoint of its length and width. In some implementations, the magnified area may be irregular in shape. In this case, the center position can be defined as the centroid of the irregular shape, or a representative anchor point predefined by the developer, such as the main control point of a polygonal hotspot. The coordinates of the center position are usually calculated based on the screen coordinate system of the graphical user interface, with the origin possibly located at the upper left corner of the screen, using pixels as the unit. During dynamic interactions, such as when the magnified area is dragged by the user, its center position updates in real time, and the system needs to continuously monitor changes in these coordinate values. Determining the center position is fundamental for subsequent coverage checks, as the system needs to compare this coordinate with the position range of the target interface element. Besides coverage checks, the center position can also serve as a reference for other functions, such as an anchor point for displaying magnified content, or a benchmark for calculating the placement of auxiliary panels outside the magnified area (such as magnification control panels).

[0042] Optionally, the position of a target interface element refers to the spatial range or representative coordinates occupied by the element in the graphical user interface. Its expression can vary depending on the element type and interface implementation. For most controls or icons, their position is typically defined by a bounding rectangle, determined by the coordinates of the top-left corner and its width and height. The system determines overlap by checking if the center point of the magnified area falls within this rectangle. For linear elements (such as underlines or dividing lines), their position may be defined by the path equation of a line segment or the coordinates of its start and end points. Overlap determination may be transformed into calculating whether the shortest distance from the center point to the line segment is less than a threshold. For point elements (such as thumbtacks on a map), their position is a specific coordinate point. Overlap determination involves calculating whether the Euclidean distance between the center point and this coordinate point is less than a tolerance range. Some complex elements may consist of multiple parts, and their position can be a collection containing multiple rectangles or paths. During implementation, the hierarchical structure of interface elements also affects position determination. For example, a button may contain two child elements: an icon and a text label. The system may need to separately determine the overlap between the center point and the areas of these two child elements, or treat the button as a single area. Position information is typically maintained by the system framework during interface rendering and stored in the model's data structure. Before performing overlap detection, it may be necessary to uniformly transform position information from different levels or coordinate systems to the screen's absolute coordinate system to ensure that the coordinates of the center point of the magnified area and the position range of the target element are compared within the same metric space.

[0043] Optionally, at least partially overlapping, the description refers to a non-empty spatial relationship between the center position of the magnified area and the position of the target interface element. The core of this relationship lies in the existence of a common point or region on the two-dimensional screen space. This relationship encompasses various scenarios, from the center point falling precisely on the boundary of the target element to the center point being completely inside the target element. Geometrically, this definition establishes a "point-domain" intersection model based on the center point, distinct from the "domain-domain" model that intersects the entire magnified area with the target element area. Specifically, the system needs to perform corresponding geometric calculations based on the definition of the target element's position. If the target element's position is a rectangular area, it determines whether the X-coordinate of the center point lies between the left and right boundaries of the rectangle, and whether the Y-coordinate lies between the top and bottom boundaries. If both conditions are met, it is considered overlapping. If the target element's position is a circular area, it calculates the distance between the center point and the center of the circle. If this distance is less than or equal to the radius of the circle, it is considered overlapping. For irregular polygonal areas, ray casting or winding number algorithms may be used to determine whether the center point is inside the polygon. The criterion of at least partial overlap introduces a degree of flexibility; for example, it can be recognized even when the center point happens to overlap a very small element boundary. In some implementations, to improve fault tolerance and user-friendliness, the system may add a tiny extended margin to the target element position, i.e., an invisible "hot zone." This way, even when the center point is close to but does not strictly enter the original area of ​​the element, it can still be judged as overlapping, which adapts to scenarios where finger touch operation has errors.

[0044] Optionally, the coverage determination method of at least partially overlapping the center position with the target interface element position differs technically from and is related to methods based on the overlap of the entire region or other feature points. The method based on the overlap of the entire region refers to determining whether there is an intersection between the magnified area (such as the entire circular or rectangular area) and the target element area. This method ensures that the magnified content seen by the user is completely within their magnified field of view, but the triggering conditions for initiating magnification may be more stringent. Center point overlap determination, on the other hand, is a more relaxed and direct triggering mechanism. It uses the user's focus (represented by the center point) as a control signal. As long as the focus points to an element, even if the border of the magnified area does not completely contain that element, it can immediately trigger a magnified preview, which aligns with the intuition of rapid positioning. Another possible determination method is to use a specific feature point within the magnified area. For example, for a directional lens, its focus may not be at the geometric center, but rather at a position slightly in front. The advantage of center point determination is its simple and efficient calculation, clear geometric meaning, and ease of user prediction and control. It can also be combined with other determination logics, such as as a preliminary quick filtering condition, first screening potential targets by the center point, and then supplementing with more accurate region overlap calculations to confirm the final coverage result. At the implementation level, using center point determination can reduce the need for complex polygon intersection tests on a large number of interface elements in each frame of rendering. This is especially beneficial when interface elements are dense and complex in shape, effectively reducing the processor's computational load. This choice of determination logic reflects an engineering trade-off between interactive sensitivity, computational performance, and visual feedback accuracy.

[0045] In an optional implementation, the method further includes: canceling the display of the magnifying control in response to the magnifying area no longer covering the functional control. This way, when the user's focus, i.e., the magnifying area, moves away from the interface position that originally contained the functional control, the magnifying control, previously displayed externally for ease of operation, can be automatically cleared, promptly eliminating invalid or outdated interface elements. This prevents screen space from being occupied by irrelevant controls, maintaining the cleanliness and timeliness of the graphical user interface. This mechanism ensures a strong real-time correlation between the magnifying control and the content currently covered by the magnifying area, allowing the display state of auxiliary operation controls to dynamically follow the user's observation intentions and browsing behavior. This reduces user confusion caused by seeing controls unrelated to the current focus, improving the consistency of interaction logic and the efficiency of human-computer interaction.

[0046] For example, on a mobile interface of a graphic design software, a user zooms in to view and manipulate a zoom control corresponding to a "Filter" function button located in the corner of the canvas. The user then drags the zoomed-in area to the other side of the canvas to view details of a drawing brush. When the boundary of the zoomed-in area completely moves outside the original screen coordinates of the "Filter" button, meaning it no longer covers the function control, the system automatically cancels the display. The "Filter" zoom control, which was previously floating outside the zoomed-in area, fades out of the interface with a fade-out animation. At this point, only the zoomed-in area and its magnified brush detail image remain on the screen, without any remaining filter controls unrelated to the current view, thus automatically optimizing the interface layout.

[0047] Optionally, the state where the zoomed-in area no longer covers the functional control describes the interruption of the spatial association between the zoomed-in area and a specific interface element. This state can occur based on various dynamic conditions. The most direct condition is a user-initiated movement operation, i.e., dragging the zoomed-in area from one screen position to another, so that the screen coordinate system range covered by the zoomed-in area no longer intersects with the display area of ​​the target functional control. For example, if the functional control is a rectangular button, the system calculates in real time the overlapping area or center point distance between the geometry of the zoomed-in area and the rectangular area. When the overlapping area is zero or the center point distance exceeds a preset threshold, it can be determined that it no longer covers the control. Another situation is that the zoomed-in area itself remains stationary, but the content of the graphical user interface scrolls or switches, causing the functional control originally located below the zoomed-in area to move out of the zoomed-in area's coverage due to the dynamic changes in the interface content. For example, in a vertically scrollable long list, the zoomed-in area is fixed in the center of the screen. When the user scrolls the list, a detail button for an item that was originally within the zoomed-in area will slide upwards and out of the zoomed-in area's view as the list item moves. Furthermore, changes in the visibility state of a functional control itself can also lead to the termination of the overlay relationship. For example, the functional control may be hidden, disabled, or destroyed by the user or other system processes. In this case, even if the coordinates of the zoomed-in area still mathematically include the original logical position of the control, the overlay relationship no longer exists because the control entity no longer exists. The system can capture these state changes through periodic polling or an event listening mechanism. The polling method checks the spatial relationship between the zoomed-in area and all known functional controls at regular intervals; the event listening method is more efficient, as it can subscribe to interface scrolling events, control state change events, and zoomed-in area movement events, re-evaluating the overlay relationship only when the relevant events are triggered, thus promptly determining whether the condition for no longer overlaying is met.

[0048] In an optional implementation, the method further includes: responding to a zoom-out or zoom-in operation where the touch start point is located within the zoom-in area, zooming out or zooming in on the target interface element within the zoom-in area; the zoom-out operation includes a two-finger pinch-to-zoom gesture, and the zoom-in operation includes a two-finger swipe gesture. This provides users with the ability to precisely adjust the viewing scale directly within the zoomed-in field of view after activating the zoom-in area and moving to the target location, without needing to exit zoom-in mode or switch tools; by limiting the starting point of the gesture operation to the zoom-in area, it clearly defines that the operation is directed at the zoomed-in content rather than the zoom-in area itself, reducing interaction ambiguity; two-finger pinch-to-zoom and swipe gestures are intuitive and universal zoom gestures, resulting in low learning costs and a natural, smooth interaction, meeting users' differentiated observation needs for interface element details in different scenarios, such as zooming in to observe textures when viewing high-resolution images, or zooming out to get an overview of the layout when reading dense text.

[0049] For example, in a mobile application displaying complex engineering drawings, a user has already invoked a circular magnifying area using a preset gesture and moved it to cover a precision part drawing on the drawing. To view the internal structural lines of the part more clearly, the user can place the initial touch points of both fingers within the display area of ​​this circular magnifying area and then perform a two-finger outward swipe. The system detects that the touch start point is within the magnifying area and the gesture is outward, and then further magnifies and renders the part drawing currently displayed within the magnifying area, allowing the user to observe finer lines and annotations. Conversely, if the user wants to know the relative position of the part in the overall drawing, they can perform a two-finger pinch gesture within the magnifying area, and the system will reduce the display scale of the part drawing within the magnifying area, thus accommodating more surrounding drawing information within the limited magnifying area's field of view.

[0050] In another specific embodiment, as shown in the appendix to the specification... Figure 5a As shown, by using a two-finger outward swipe with the touch starting point within the magnification area 501, the user further magnifies the already magnified interface element 502 in the magnification area 501 into a larger interface element 503; by using a two-finger convergence swipe with the touch starting point within the magnification area 501, the user updates the already magnified interface element 502 in the magnification area 501 into a smaller interface element 504. It should be noted that the two-finger operation is not limited to two fingers of the same hand, but can also be a touch operation using fingers of different hands (such as the operation of the left and right thumbs); it is not limited to a swipe operation using only two fingers, but can also be a touch operation using two or more fingers; in addition to swiping with two or more fingers simultaneously, it can also be a swipe operation where only some fingers swipe, while the other fingers only maintain contact with the touch screen.

[0051] Optionally, the condition that the touch start point is located within the magnified area constitutes an important criterion for determining the operational context. While continuously monitoring touch events, the system needs to determine in real time whether the coordinates of the user's finger when it first touches the screen are within the boundary of the currently displayed magnified area. This determination is typically calculated based on the screen coordinate system and the geometry occupied by the magnified area. For example, if the magnified area is rendered as a circle, the system calculates the distance between the touch point and the center of the circle. If this distance is less than or equal to the radius of the circle, the start point is determined to be within the area; if the magnified area is a rectangle, the system checks whether the X and Y coordinates of the touch point are between the left and right boundaries and the top and bottom boundaries of the rectangle, respectively. This determination mechanism distinguishes touch gestures occurring inside the magnified area from those occurring outside, thus assigning different semantics to the same or similar gesture patterns. For example, with the same two-finger pinch gesture, if the start point is inside, it means the user wants to zoom in on the magnified content view; if the start point is outside, it may correspond to a different set of interaction logic, such as adjusting the size of the magnified area itself. This spatial location-based intent differentiation allows limited touch gestures to be mapped to a richer set of functions, enhancing the capacity and efficiency of interaction. In implementation, the system may need to process the starting position of each touch point in a multi-touch event and apply specific aggregation logic. For example, it might require that at least two touch points' starting positions are within the zoom area, or that the starting position of the primary touch point (such as the finger that first touches the screen) is within the area, before triggering a content zoom operation. This ensures the explicitness of the operation and prevents accidental touches.

[0052] Optionally, in response to a zoom-in or zoom-out operation where the touch originates within the zoomed-out area, the target interface element can be zoomed in or out. This step implies an implicit understanding of the user's intent and a dynamic adjustment of the rendered content. The zoom-in or zoom-out operation here does not target the container holding the content (i.e., the zoomed-out area), but rather the visual content currently presented within that container—the image data of the target interface element being zoomed in. When performing this operation, the system typically maintains the screen position, shape, and physical size of the zoomed-out area unchanged, but changes the transformation matrix of its internal rendered content, such as increasing or decreasing a scaling factor. When the user performs a zoom-in operation (two fingers outward), the system increases the scaling factor, making the target interface element's drawing size within the zoomed-out area larger, thus revealing more detail. However, this may simultaneously reduce the field of view of the zoomed-out area, meaning only a smaller portion of the original target element may be visible. When the user performs a zoom-out or zoom-in operation, the system decreases the scaling factor, making the target interface element's drawing size within the zoomed-out area smaller, thus allowing a larger portion of the target element or more of the surrounding interface content to be displayed within the same zoomed-out area. This process requires high real-time performance. The system needs to follow the continuous movement of the user's fingers, dynamically calculate the rate of change or absolute displacement of the distance between the fingertips, and map it to continuous scaling level changes to provide smooth scaling animation feedback. From a technical implementation perspective, this involves off-screen rendering or texture sampling of the original interface elements or their corresponding view hierarchy, and then applying dynamic scaling transformations to redraw within the specific viewport of the zoomed-in area.

[0053] Optionally, zooming out includes a two-finger pinch-to-zoom gesture, and zooming in includes a two-finger swipe outwards. This defines the specific form of the touch gesture. A two-finger pinch-to-zoom gesture typically refers to the user simultaneously touching the screen with two fingers (such as the thumb and forefinger), maintaining contact while moving the two fingers in a direction that is generally closer together, causing the screen distance between the two touch points to continuously decrease. Conversely, a two-finger swipe outwards gesture involves the two fingers touching the screen and then moving them in a direction that is further apart, causing the screen distance between the two touch points to continuously increase. These two gestures are widely adopted and well-known metaphors for zooming in and out on touch devices. In the context of the zoomed-in area interaction, the system needs to accurately capture these two gesture patterns. In implementation, the system tracks the trajectory of each touch point and calculates a value representing the degree of gesture zoom, such as the change in the Euclidean distance between the two touch points relative to the initial distance, or the change in the angle between the vectors formed by the two fingers. A pinch-to-zoom gesture corresponds to this ratio being less than 1 or continuously decreasing, while a swipe outwards gesture corresponds to a ratio greater than 1 or continuously increasing. The system sets a minimum displacement threshold or scaling threshold for these two types of gestures to distinguish between intentional scaling operations and unintentional slight finger tremors. Furthermore, gesture recognition also needs to consider time factors; for example, the gesture must reach a certain speed or displacement within a specified time to be recognized as a valid scaling command. In some advanced implementations, the system may also combine the gesture's starting area and direction for a comprehensive judgment to further improve recognition accuracy.

[0054] Optionally, limiting the touch start point within the magnified area serves not only to distinguish operational intentions but is also closely related to interaction state management and user cognitive models. The magnified area can be viewed as a temporarily activated floating window with an independent interaction modality. When the user's touch start point falls within this window, it's equivalent to the user explicitly focusing their attention and operational focus on the content of that window. The system then interprets subsequent gestures as commands to manipulate the content of that window itself. This design aligns with the focus-context interaction model, reducing the uncertainty of the system state. From a user's perspective, they easily understand that "pinching your fingers in a magnifying glass magnifies what you see." This consistency in interaction logic helps form a stable mental model. In practical applications, the system may need to handle gesture conflicts or combined gestures. For example, a user might begin an outward expansion gesture with two fingers within the magnified area, but during the gesture, one finger temporarily moves outside the magnified area's boundary. Different systems may have different handling strategies for this: some might continue to recognize the gesture as content zooming until the gesture ends, while others might immediately stop the zooming operation when the finger goes outside the boundary. Furthermore, zooming within the zoomed-in area may coexist with other operations. For example, on devices supporting multi-touch, a user might use a third finger to perform other operations outside the zoomed-in area simultaneously. The system needs to properly manage these concurrent input events to ensure the accuracy and predictability of the interaction.

[0055] In an optional implementation, the method further includes: responding to a zoom-out or zoom-in operation where the touch start point is outside the zoom-in area, reducing or increasing the size of the zoom-in area; the zoom-out operation includes a two-finger pinch-to-slide operation, and the zoom-in operation includes a two-finger outward pinch-to-slide operation. This provides users with a means of adjusting the size of the zoom-in area itself, independent of the operation on the displayed content. By distinguishing the spatial location of the operation start point (outside the area), the operation intention is separated, allowing users to flexibly adjust the visual coverage of the magnifying glass without precisely touching the boundary or interior of the zoom-in area. This design allows users to dynamically adapt the physical size of the zoom-in area according to the size and density of the interface elements to be observed, or personal operating habits. For example, when viewing dense small icons, the zoom-in area can be enlarged to obtain a wider field of view, or the zoom-in area can be reduced to focus on a smaller area when precisely locating a single pixel, thereby enhancing the adaptability and operational freedom of the zoom function and improving the fine control of the interaction.

[0056] For example, in the mobile interface of a map navigation application, a user activates a circular zoom-in area on the map using a preset touch operation to view detailed road signs at a specific intersection. The user finds that the zoom-in area is fixed in size and cannot fully cover the complex intersection diagram. The user can place two fingers simultaneously on any blank area of ​​the screen outside the zoom-in area, such as the lower right corner, and then perform a two-finger outward swipe operation, sliding the two fingers in opposite directions (upper left and lower right). Since the starting point of this touch operation is clearly outside the zoom-in area, the system recognizes this gesture as a zoom-in operation targeting the zoom-in area size and responds by dynamically increasing the radius of the circular zoom-in area. The boundary of the zoom-in area expands outward, covering more map area and bringing more road sign information that was originally at the edge of the area into the zoomed-in display range. Conversely, if the user wants the zoom-in area to focus more intently on a specific traffic sign, they can place two fingers on another location outside the zoom-in area and perform a pinch swipe. The system will then correspondingly reduce the size of the zoom-in area, shrinking its coverage area and further magnifying the image in the central area, thus making the details of the target sign more prominent.

[0057] In another specific embodiment, as shown in the appendix to the specification... Figure 5b As shown, by using a two-finger outward swipe with the touch starting point outside the magnified area 501, the user can further magnify the magnified area 501 into a larger magnified area 505. The display size of the interface elements 502 in both magnified areas 501 and 505 remains unchanged, but the latter contains more content. Conversely, by using a two-finger convergence swipe with the touch starting point outside the magnified area 501, the user can shrink the magnified area 501 into a smaller magnified area 506. The display size of the interface elements 502 in both magnified areas 501 and 506 remains unchanged, but the latter contains less content. It should be noted that the two-finger operation is not limited to two fingers of the same hand; it can also be a touch operation using fingers from different hands (e.g., left and right thumbs); it is not limited to a swipe using only two fingers; it can also be a swipe using more than two fingers; besides swiping with two or more fingers simultaneously, it can also be a swipe using only some fingers while the other fingers remain in contact with the touchscreen.

[0058] Optionally, the condition that the touch start point is located outside the magnified area defines the initial position constraint of the input gesture that triggers the magnified area size transformation operation in screen space. This condition is a key technical feature for achieving operation intent separation, and it relies on the system's real-time judgment of the geometric relationship between the touch event coordinates and the magnified area display area. The touch start point usually refers to the set of coordinate points corresponding to all participating fingers at the moment of contact with the screen in a multi-touch gesture. To determine whether these start points are located outside the magnified area, the screen coordinates of each touch point need to be compared with the pixel area currently occupied by the magnified area; the condition is satisfied if and only if the coordinates of all touch start points fall outside the range defined by the magnified area (e.g., its boundary rectangle or circular outline). This judgment can prevent conflicts and misidentification with touch operations within the magnified area (such as scaling the magnified area content as described in claim 7). For example, the magnified area may be a semi-transparent circular overlay. When the system detects a two-finger touch event, it immediately obtains the initial coordinates of the two touch points and calculates the relationship between these coordinate points and the center and radius of the circular area. If the distance between both points and the center of the circle is greater than the radius of the circle, the starting point is considered to be outside the area. This determination needs to be completed within the first few milliseconds of the touch event to ensure the correctness of subsequent gesture processing. In actual interaction, users may start gestures from the edge of the screen or from a position a certain distance away from the magnified area, which provides ample room for size adjustment and avoids fingers obscuring the content of the magnified area. The design of this condition also considers the discoverability of the operation; users can naturally discover this function of adjusting the size of the area by trying to perform operations that conform to the zoom gesture specifications outside the magnified area.

[0059] Optionally, the size of the magnified area refers to the physical display area occupied by this visual component in the graphical user interface. Size is a multi-dimensional geometric attribute, and its definition varies depending on the shape of the magnified area. For the most common circular magnified area, its size is usually defined by its radius or diameter; for rectangular magnified areas, the size is defined by its width and height. Changes in size directly determine the area of ​​the original interface content that the magnified area can cover and enlarge. For example, a circular magnified area with a radius of 50 pixels has a fixed coverage area; when the size is enlarged, increasing the radius to 80 pixels, the area of ​​the original interface it covers expands from a smaller circle to a larger one. Size adjustments are usually driven by continuous user gesture input, allowing for smooth animation transitions, causing the boundaries of the magnified area to gradually expand or contract. In addition to the overall size, changes in the size of the magnified area may also be accompanied by adaptations to other visual attributes. For example, the stroke width of the area's edges may need to be adjusted proportionally to maintain visual balance, or the magnification at the center of the area may need to be adjusted inversely when the area size changes to ensure the continuity of the magnification effect. The upper and lower limits of the size can also be set to prevent the magnified area from being too large to cover the entire screen and lose its focus, or too small to effectively display the content.

[0060] Optionally, the two-finger outward swipe gesture is a multi-touch gesture opposite to the two-finger pinch gesture, used to express the interaction intention of magnification or expansion. In this gesture, the user's two fingers simultaneously touch the screen and, while maintaining contact, each finger slides in a direction that increases the distance between them. The trajectory is represented by the two touch points separating in opposite directions from a relatively close starting position; for example, one finger slides to the upper left and the other to the lower right. The system recognizes this gesture by monitoring the coordinates of the two touch points in real time and calculating the real-time change in their distance. The key judgment logic is whether the distance continuously increases and whether the increase exceeds a system-set recognition threshold. For accurate recognition, the system needs to distinguish this gesture from other possible two-finger swipes, such as parallel swipes or rotational swipes, which can be achieved by analyzing the angle between the two finger movement direction vectors and the midpoint displacement. During the gesture execution, the system not only detects changes in distance but also calculates the rate of change; rapid outward swipes may lead to a rapid increase in the magnified area size, while slow outward swipes allow for more precise size adjustments. From an ergonomic perspective, the two-finger outward gesture naturally maps to the mental model of "expanding" or "enlarging" an object, making it easy for users to understand and remember. In practical implementation, the system may define an effective area for this gesture, meaning the touch start point must be outside the enlarged area, but the entire swipe of the gesture can cross any area of ​​the screen, as long as the fingers do not leave the screen. The gesture typically ends when at least one finger leaves the screen, at which point the system records the final size value. In some interaction schemes, this gesture can also be combined with other modifiers. For example, while expanding with two fingers, keeping the relative position of the finger contact point to the center of the enlarged area unchanged allows for proportional enlargement with the area center as the anchor point, thus providing richer dimensions of size control.

[0061] In an optional implementation, the method further includes: canceling the display of the magnified area in response to a sliding rate greater than a preset rate for a zoom-out operation on the magnified area; the zoom-out operation includes a two-finger pinch-and-slide operation with the touch starting point outside the magnified area or a sliding operation with the touch starting point at the boundary of the magnified area. This provides an efficient and quick way to close the magnified area by recognizing a specific zoom-out gesture with a high sliding rate as a quick close command, distinguishing between slow operations intended for fine-tuning the area size and fast operations intended for quickly canceling the magnified view. Users do not need to find a specific close button or perform additional confirmation steps; they can quickly exit the magnified mode simply by accelerating the sliding based on familiar gesture operations. This is particularly suitable for scenarios requiring quick view switching or temporary magnification followed by an immediate return to the main interface, greatly improving interaction efficiency and operational smoothness, and creating a natural, coherent, and efficient interactive loop for enabling and disabling the magnification function.

[0062] For example, in the touch interface of an image editing application, a user brings up a circular zoom-in area by swiping around a complex icon to fine-tune the icon's edge pixels. After editing, the user wants to quickly close the zoom-in area to view the overall canvas. The user can place two fingers on the circular boundary of the zoom-in area and then quickly perform a short, rapid two-finger pinch-and-swipe gesture. The system detects that the touch origin of this gesture is at the boundary of the zoom-in area and calculates the instantaneous speed of the finger swipe in real time. When the calculated swipe speed exceeds a system-defined speed threshold (e.g., 500 pixels per second), the system determines that the user's intention is not to slowly shrink the zoom-in area, but to quickly close it. Therefore, the system immediately responds to the operation, triggering a smooth disappearing animation to remove the zoom-in area from the interface in a short time, and the user's view returns to the un-zoomed global canvas. Similarly, the user can also choose to quickly perform a two-finger pinch-and-swipe gesture outside the zoom-in area to achieve the same quick closing effect.

[0063] Optionally, the preset rate is a threshold parameter used to determine whether a user's gesture intent is a quick cancellation operation. It is a predefined speed value representing the critical point that distinguishes between regular operations and quick cancellation operations. In the context of touch interaction, the swipe rate usually refers to the average or instantaneous speed at which a touch point (such as a finger) moves across the screen surface, and its unit can be pixels per second or centimeters per second. The preset rate can be set based on experimental data, ergonomic analysis, or the specific needs of the application scenario. For example, it can be set to a higher speed value that is clearly distinguishable from slow swipes performed by the user to finely adjust the size of the zoomed-in area. In actual system implementation, the preset rate may not be a fixed value but can be dynamically adjusted according to the context, such as considering the size of the current zoomed-in area, the screen size of the device, or the user's historical operating habits. When the system detects a gesture that matches the definition of a zoom-out operation, it continuously tracks the movement trajectory of the touch point and estimates the swipe rate in real time by calculating the distance moved per unit time. This calculation process may involve sampling and filtering the original touch coordinate sequence to remove jitter, and applying a physical motion model to obtain a smooth speed estimate. Comparing the estimated real-time swipe rate with the preset rate is a crucial logical step: if the real-time rate consistently exceeds the preset rate, a quick cancellation process is triggered; otherwise, the regular zoom-in area adjustment process begins. The existence of the preset rate allows a single gesture (two-finger pinch) to be mapped to two distinctly different system responses depending on its execution speed, thereby enriching the semantics of the gesture and improving the interaction bandwidth.

[0064] Optionally, the condition that the swipe rate is greater than a preset rate forms the core decision for triggering the rapid cancellation mechanism of the zoomed-in area. This condition is a dynamic, kinematic measurement-based judgment that requires the system to not only recognize the type of gesture (two fingers pinching together) but also quantify the intensity or urgency of its execution. When the user performs a zoom-out operation, the system obtains the displacement and time data of the finger movement from the touch event stream. The swipe rate can be calculated in real time during the gesture, for example, by estimating the instantaneous rate by monitoring the displacement and time differences between the most recent sampling points; or by calculating the average rate based on the total displacement and total time when the gesture ends or reaches a certain stage. A comparison result greater than the preset rate indicates that the user's operation has changed from an "adjust" intention to a "close" intention. This design utilizes the user's natural behavior pattern: when the user wants to adjust the size slowly, their gesture is usually smooth and slow; while when the user wants to close quickly, their gesture tends to be short and fast. The system separates these two behavior patterns through the preset rate filter. In terms of technical implementation, this comparison may be completed by a conditional statement, the output of which is a Boolean value used to control the branching flow of the program. Setting this condition requires balancing the risk of false triggering with ease of operation. A preset rate that is too high may make it difficult to trigger quick shutdown, resulting in a poor user experience; a preset rate that is too low may cause normal size adjustment operations to be misinterpreted as shutdown operations. Furthermore, the system can incorporate other sensor data or contextual information to assist in this judgment, such as combining the acceleration trend of the gesture, making the judgment more robust and accurate.

[0065] Optionally, the complete response process of canceling the display of the magnified area in response to a sliding rate exceeding a preset rate during a zoom-out operation reflects the system's automated control logic for recognizing, judging, and executing corresponding state transitions based on composite input conditions. The entire process begins with capturing the original touch input event. The system first needs to identify that this is a multi-touch gesture conforming to the definition of a zoom-out operation, i.e., a two-finger pinch-and-swipe gesture. Next, the system needs to verify two key attributes in parallel or sequentially: first, the spatial location attribute of the touch starting point, which must fall under one of the two conditions defined in the claims—either entirely outside the magnified area, or at least one point within the boundary area of ​​the magnified area; second, the dynamic attribute of the gesture, i.e., its sliding rate needs to be calculated in real time and compared with a preset rate threshold. Only when both conditions are simultaneously met will the entire response chain be activated, leading to the result of canceling the display. If only the location condition is met but the sliding rate is insufficient, the conventional size adjustment described in claim 8 may be triggered; if the sliding rate is fast but the starting point location does not meet the requirements (e.g., entirely within the magnified area), other logic may be triggered or the operation may be considered invalid. Once the conditions are met, the system generates an internal command or event to cancel the display. This command triggers the interface rendering module to perform a visual hiding operation and notifies the interaction state management module to update the state. The response time of the entire process should be as short as possible to ensure that the user experiences the immediacy of the operation. This response mechanism combines the spatial characteristics (starting point) of the gesture with the temporal dynamic characteristics (speed), creating an efficient, intuitive, and accident-resistant mode switching method.

[0066] In an optional implementation, the preset touch operation includes a swipe gesture around the target interface element. This provides users with an intuitive and metaphorical gesture to actively invoke the magnified view. This gesture, by drawing a closed or approximately circular trajectory around the target interface element, clearly and unambiguously conveys to the system the specific object the user intends to magnify, avoiding accidental touches or selection difficulties caused by densely packed or small interface elements. The circling gesture simulates the action of circling a key point with a fingertip in real life, conforming to the user's natural cognition and reducing the learning cost. Simultaneously, because the touch trajectory of this gesture naturally defines the approximate range of the target, the system can more accurately locate the core area of ​​the user's intended operation, thereby quickly and accurately triggering the magnified display, improving the certainty and efficiency of the interaction.

[0067] For example, in an industrial monitoring application with a complex dashboard interface, the screen displays numerous densely packed small status indicator lights and numerical labels. When an operator needs to view a specific pressure gauge icon in detail, they don't need to painstakingly click on the tiny icon; they can simply use one finger to perform a roughly circular swipe around the outer area of ​​the pressure gauge icon. The system continuously monitors the finger's touch trajectory, and when it recognizes that the swipe path forms a spatial loop around the pressure gauge icon, it determines that the user has performed a preset touch operation on the pressure gauge icon. Subsequently, the system immediately generates and displays a magnified area at the location of the pressure gauge icon, magnifying the icon and its internal fine scale and pointer readings for clear viewing by the operator.

[0068] Optionally, a swipe gesture around a target interface element is a specific gesture input paradigm. Its core lies in the trajectory path formed by the movement of a touch point (such as a finger or stylus) on a touch-sensitive surface, which spatially encircles a specific display element in the graphical user interface (i.e., the target interface element). From a gesture recognition perspective, this operation typically begins at a point outside the target interface element, then the touch point moves, its trajectory at least partially encircling the target interface element, potentially forming a complete or incomplete circle, ellipse, or other polygonal loop, ultimately ending near the starting point or at another location. The system's detection and judgment of this operation does not require the trajectory to be a geometrically perfect closed shape, but can be calculated based on the spatial relationship between the sequence of trajectory points and the position of the target interface element. For example, the system can track the coordinates of the touch point in real time and calculate the azimuth and distance changes between these coordinate points and the center point or boundary of the target interface element. When a touch point is detected to have moved around a target element beyond a certain angle (e.g., more than 270 degrees), and the average distance between the touch point and the target element remains within a reasonable range throughout the movement (neither too far to lose connection, nor too close to be considered a direct swipe on the element), a wraparound operation can be determined to have occurred. This algorithm allows users to draw wraparound trajectories in a more casual and ergonomic manner, improving the naturalness and error tolerance of gestures. From an interaction semantics perspective, this operation explicitly anchors the user's attention and operational intent to a specific interface object, providing higher precision in object specification compared to aimless swiping or clicking.

[0069] Optionally, the swipe path in a wraparound operation possesses specific spatial and dynamic attributes. This path unfolds in a two-dimensional screen coordinate system, and its shape, size, direction, and speed can be diverse. The shape of the path is typically expected to be circular, but not limited to a perfect circle; it can be an ellipse, a rectangle with rounded corners, or even an irregular curve, as long as its overall trend is to wrap around the target interface element once or most of the time. The size of the path, i.e., the radius or range of the wraparound, is usually determined by the initial distance between the user's finger and the target element when swiping and their distance control habits during the swipe. The system focuses more on relative positional changes than absolute distances during recognition. The direction of the path, i.e., whether the user swipes clockwise or counterclockwise, usually does not affect the basic recognition of the operation; the system can treat both directions equally, providing users with operational freedom. The swipe speed can also vary within a certain range. The system distinguishes between intentional gestures and accidental, aimless swiping by setting reasonable time thresholds. For example, an effective wraparound operation may require completing most of the trajectory within a preset maximum time limit to ensure responsiveness of the interaction. In some implementations, the system may also evaluate the smoothness of the sliding path; overly abrupt or jagged trajectories may be considered invalid input. Furthermore, the criteria for determining whether a sliding operation "wraps" around the target element can be flexible. For example, for a linearly arranged set of small elements (such as icons in a list), if a user makes a sliding operation that roughly wraps around the set of elements, the system can intelligently identify that set of elements or the element closest to the geometric center of the sliding path as the target interface element.

[0070] Optionally, the specific parameters and recognition thresholds for the wrap-around swipe operation can be configured and adaptively adjusted according to different application scenarios or user preferences. For example, the system can allow users or developers to set the minimum angle coverage threshold required for the wrap-around operation to take effect. A lower threshold makes the gesture easier to trigger, suitable for environments requiring fast operation; a higher threshold requires a more complete gesture, helping to prevent accidental triggering. Another adjustable parameter is the maximum allowable average distance between the touch trajectory and the target element, which defines the tightness of the "wrap-around". In addition, the system can support setting the tolerance for wrap-around speed to accommodate the different gesture speed habits of different users. There are also some natural variations of the wrap-around operation. For example, in addition to single-finger wrap-around, the system can also recognize two-finger collaborative wrap-around gestures, such as two fingers drawing arcs towards each other from both sides of the element and then converging, which also conveys the wrap-around intention. Another variation is "tap-then-wrap-around", where the user first taps the target element (indicating selection), and then performs a short arc swipe near the element to trigger zoom-in, which combines the two steps of selection and gesture confirmation. In some implementations, the system can provide visual feedback during the user's swipe, such as drawing a semi-transparent halo along the finger's path or making the surrounded target element emit a bright pulse to indicate that the user's gesture is being recognized, enhancing the visibility and guidance of the interaction. The adjustment of these parameters and the support for variations allow the wrap-around operation to flexibly adapt to the needs of different precision levels and usage environments, ranging from consumer electronics devices to professional industrial touchscreens.

[0071] In an optional implementation, the magnified area is circular. This circular shape fully leverages the inherent visual and interactive advantages of a circle. The circular geometric center is clear and unique, allowing users to intuitively determine the center coverage point of the magnified area, facilitating precise target positioning and tracking. Its uniform and symmetrical outline, without sharp edges, provides a smooth and continuous visual transition during movement or zooming, reducing visual interference and abruptness. Simultaneously, the circular boundary better conforms to the contact surface of a finger or stylus, resulting in a more natural and fluid operation when performing edge dragging, movement, or zooming gestures, conforming to ergonomic principles. This overall enhances the ease of use, accuracy, and user experience of the magnification viewing function.

[0072] For example, in a medical image viewing application, a high-resolution digital image of a pathological slide is displayed on the screen, filled with dense cellular tissue. Radiologists need to carefully examine the morphological details of cells in a suspected lesion area. When the doctor uses a specific gesture to bring up a circular magnifying area in that area, this circular area floats above the image like a transparent magnifying glass. Because the magnifying area is circular, its center point is very prominent, allowing the doctor to easily align this point with the specific cell nucleus they want to observe. When dragging this circular magnifying area for scanning, its rounded edges blend more naturally with the complex cellular background image, avoiding the harsh right-angle cut of a square magnifying frame, helping the doctor maintain continuity of observation. The circular outline also makes it smoother and more controllable for the doctor to adjust the size of the magnifying area using finger pinch gestures.

[0073] Optionally, the edge area of ​​the circular magnified region plays a crucial role in the interaction, and its design requires careful consideration of the coordination between the touch hotspot, gesture recognition boundaries, and visual feedback. Since the magnified region needs to respond to user touch operations such as movement and zooming, its edge must be defined as an effective touch hotspot. For a circle, this hotspot can be designed as a ring-shaped area surrounding the circumference. The width of this ring-shaped hotspot needs careful calibration: too small a width will make it difficult for users to touch accurately, reducing the success rate of operations; too large a width may occupy too much screen space or cause touch conflicts with other adjacent interface elements. When detecting touch events, the system needs to determine whether the touch point falls within this ring-shaped hotspot. When a touch event occurs, the visual feedback needs to be synchronized with the touch position and operation intention. For example, when a user's finger presses on the edge of the circular magnified region, the brightness, color, or thickness of that edge area can change slightly to indicate that the user has successfully grasped the control. During movement, visual feedback can manifest as the entire circular area smoothly translating as the finger is dragged; in zoom gestures, the circumference contracts or expands in real time as the finger is brought together or extended. The continuity of the circle ensures that these visual feedbacks are consistent and seamless at any point along the edge.

[0074] Exemplary embodiments of this disclosure also provide a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the methods described above.

[0075] In one implementation, the computer program product can be a tangible product containing a computer program, such as a computer-readable storage medium storing the computer program. The readable storage medium can be a storage medium based on electrical, magnetic, optical, electromagnetic, infrared, or other signals, including but not limited to: random access memory (RAM), read-only memory (ROM), magnetic tape, floppy disk, flash memory, hard disk drive (HDD), solid-state drive (SSD), etc. For example, the computer program product can be implemented as a non-volatile storage medium storing a computer program, such as read-only memory, NAND flash memory, etc.

[0076] In one implementation, the computer program product can be an intangible product containing a computer program. For example, the computer program product can be implemented as a virtual digital product, such as an executable file, installation package, or other digital file storing the computer program.

[0077] Computer program code can be written in one or more programming languages. Examples of programming languages ​​include C, Java, and C++. Program code can execute entirely on the user's computing device, partially on the user's computing device, or as a standalone software package. It can also execute partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, such as a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via an internet connection provided by a mobile network operator).

[0078] Computer programs can be carried or transmitted via signals such as electricity, magnetism, light, electromagnetic radiation, and infrared radiation. Electronic devices can convert signals carrying computer programs into digital signals, thereby running the computer programs. When a computer program runs on an electronic device, its code is used to cause the electronic device to execute (more specifically, to be executed by the processor of the electronic device) the method steps of various exemplary embodiments of this disclosure, such as: an information processing method, including: providing an information input entry point; receiving user input information; displaying a channel selection interface, wherein the channel selection interface displays at least one candidate channel; determining a target channel from the candidate channels; and sending the user input information to the target channel.

[0079] Exemplary embodiments of this disclosure also provide an electronic device. The electronic device may include a processor and a memory. The memory stores executable instructions for the processor, such as a computer program. The processor executes the executable instructions to perform the method steps of various exemplary embodiments of this disclosure. Furthermore, the electronic device may also include a display for displaying a graphical user interface.

[0080] The following is for reference. Figure 6 The electronic device is illustrated by way of a general-purpose computing device. It should be understood that... Figure 6 The electronic device 600 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0081] like Figure 6 As shown, the electronic device 600 may include: a processor 610, a memory 620, a bus 630, an I / O (input / output) interface 640, a network adapter 650, and a display 660.

[0082] Memory 620 may include volatile memory, such as RAM 621 and cache unit 622, and may also include non-volatile memory, such as ROM 623. Memory 620 may also include one or more program modules 624, such program modules 624 including, but not limited to: operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. For example, program module 624 may include the modules in the above-described device.

[0083] The processor 610 may include one or more processing units, such as an AP (Application Processor), a modem processor, a GPU (Graphics Processing Unit), an ISP (Image Signal Processor), a controller, an encoder, a decoder, a DSP (Digital Signal Processor), a baseband processor, and / or an NPU (Neural-Network Processing Unit).

[0084] The processor 610 can be used to execute executable instructions stored in the memory 620 to perform the methods described above in this disclosure, such as the following method steps: an information processing method, comprising: providing an information input entry point; receiving user input information; displaying a channel selection interface, wherein the channel selection interface displays at least one candidate channel; determining a target channel from the candidate channels; and sending the user input information to the target channel.

[0085] Bus 630 is used to connect different components of electronic device 600 and may include a data bus, an address bus and a control bus.

[0086] Electronic device 600 can communicate with one or more external devices 700 (such as keyboard, mouse, external controller, etc.) through I / O interface 640.

[0087] Electronic device 600 can communicate with one or more networks via network adapter 650. For example, network adapter 650 can provide mobile communication solutions such as 3G / 4G / 5G, or wireless communication solutions such as wireless LAN, Bluetooth, and near-field communication. Network adapter 650 can communicate with other modules of electronic device 600 via bus 630.

[0088] Electronic device 600 can display a graphical user interface, such as virtual scenes or virtual characters, through display 660.

[0089] although Figure 6 Other hardware and / or software modules may also be configured in the electronic device 600, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (Redundant Arrays of Independent Disks) systems, tape drives, and data backup storage systems.

[0090] As can be seen from the above, the technical solutions disclosed herein can be implemented as methods, apparatus, systems, computer program products, storage media, electronic devices, etc. Those skilled in the art will understand that various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which may be referred to as "circuit," "module," or "system," respectively.

[0091] It should be understood that this disclosure is not limited to the specific methods, steps, or structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. Those skilled in the art will readily conceive of other embodiments based on the specific implementations provided in this disclosure. Therefore, the specific implementations provided in this disclosure are merely exemplary, and the scope and spirit of this disclosure are indicated by the claims, and should cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary technical means in the art not disclosed in this disclosure.

Claims

1. An information processing method, characterized in that, The method includes: In response to a preset touch operation on a target interface element in a graphical user interface, a magnified area is displayed at the location of the target interface element, and the target interface element is magnified and displayed in the magnified area. In response to a movement operation of the zoomed-in area, the zoomed-in area is moved on the graphical user interface, and the target interface elements in the zoomed-in area are updated and displayed according to the position covered by the zoomed-in area.

2. The method according to claim 1, characterized in that, The method further includes: In response to the target interface element covered by the magnified area containing a prompt message, the prompt message is displayed outside the magnified area.

3. The method according to claim 1, characterized in that, The method further includes: In response to the target interface element covered by the magnified area containing a functional control, a magnified control of the functional control is displayed outside the magnified area; In response to a touch operation on the magnification control, the function of the corresponding function control is executed.

4. The method according to claim 3, characterized in that, If the target interface element covered by the magnified area contains multiple functional controls, the magnified control that displays the functional controls outside the magnified area includes: A magnified control that centrally displays the multiple functional controls outside the magnified area.

5. The method according to claim 1, characterized in that, The enlarged area covers interface elements in the following ways: the center of the enlarged area at least partially overlaps with the position of the target interface element.

6. The method according to claims 3-4, characterized in that, The method further includes: In response to the zoomed-in area no longer covering the functional control, the zoomed-in control is de-displayed.

7. The method according to claim 1, characterized in that, The method further includes: In response to a zoom-out or zoom-in operation where the touch start point is located within the zoom-in area, the target interface element in the zoom-in area is zoomed out or zoomed in; the zoom-out operation includes a two-finger pinch-to-zoom operation, and the zoom-in operation includes a two-finger outward pinch-to-zoom operation.

8. The method according to claim 1, characterized in that, The method further includes: In response to a zoom-out or zoom-in operation where the touch start point is outside the zoom-in area, the size of the zoom-in area is reduced or enlarged; the zoom-out operation includes a two-finger pinch-to-slide operation, and the zoom-in operation includes a two-finger outward pinch-to-slide operation.

9. The method according to claim 1, characterized in that, The method further includes: In response to a sliding rate greater than a preset rate for a zoom-out operation on the zoomed-out area, the zoomed-out area is canceled from display; the zoom-out operation includes a two-finger pinch-to-slide operation with the touch starting point located outside the zoomed-out area or a slide operation with the touch starting point located at the boundary of the zoomed-out area.

10. The method according to claim 1, characterized in that, The preset touch operation includes: a swipe operation around the target interface element.

11. The method according to claim 1, characterized in that, The magnified area is circular.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method according to any one of claims 1 to 11.

13. An electronic device, characterized in that, include: processor; Memory for storing the executable instructions of the processor; The processor is configured to execute the method of any one of claims 1 to 11 by executing the executable instructions.

Images