Method and device for integrating and outputting cross-page table data, equipment and medium

Abstract

Embodiments of the present application provide a cross-page table data integration output method and device, equipment and medium. The method comprises: in response to a received first operation, obtaining table data in a selected range of each of a plurality of pages, the selected range of each of one or more pages of the plurality of pages being used to represent a partial data area in a table of the page; the first operation comprises a selection operation of selecting a selected range in at least one page through at least one in-page interaction mode in at least two pages of the plurality of pages switched out through a navigation operation; the at least one in-page interaction mode comprises a box selection operation based on dragging; obtaining summary table data based on the table data in the selected range of each page; and generating an output file in a predetermined format according to the summary table data. The technical scheme of the embodiments of the present application solves the problems of complicated and error-prone operation of cross-page table data integration output in related technologies.

Description

Technical Field

[0001] This application relates to the field of spreadsheet data processing technology, and in particular to a method and apparatus for integrating and outputting cross-page spreadsheet data, an electronic device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] In modern data analysis, test and measurement, and enterprise management software, tables are a core component for carrying and displaying structured data. When the data volume is large, the interface typically uses a pagination mechanism for display. Users often need to extract data from specific areas (such as continuous rows and columns or discrete cells) from tables spanning multiple pages, and then integrate and output them as complete images, PDF documents, or reports for result verification, report preparation, or collaborative sharing. This need is particularly common and important in scenarios such as test result recording and experimental data analysis; efficiently completing this operation directly relates to work efficiency and the professionalism of the results.

[0003] In related technologies, when dealing with such cross-page data extraction and integration needs, it is usually only possible to manually take paginated screenshots and then stitch them together, or to use a special long scrolling screenshot tool. However, the former is cumbersome and prone to errors; the latter can only capture continuous visual interfaces and cannot handle the pagination logic of tables, nor does it support intelligent selection and structured reorganization of specific data areas in non-continuous pages, resulting in a lack of effective means to integrate and output cross-page table data. Summary of the Invention

[0004] This application discloses a method, apparatus, device, computer-readable storage medium, and computer program product for integrating and outputting cross-page table data, in order to solve the problem that the operation of integrating and outputting cross-page table data is cumbersome and prone to errors in related technologies.

[0005] Firstly, this application provides a method for integrating and outputting cross-page table data, which includes:

[0006] In response to a received first operation, table data within a selected range of each of multiple pages is obtained, wherein the selected range of each of one or more pages in the multiple pages represents a partial data area in the table of that page; the first operation includes a selection operation performed by at least one in-page interaction method on at least two of the multiple pages switched through a navigation operation, selecting a selected range of at least one page, wherein the one or more pages include at least one page; the at least one in-page interaction method includes a drag-based selection operation; summary table data is obtained based on the table data within the selected range of each page; and an output file in a predetermined format is generated based on the summary table data.

[0007] Therefore, by limiting the data collection to at least two pages that can be accessed through navigation, users can freely specify all or part of the data area of ​​each page through page-based interactive methods such as selection boxes, and integrate them to obtain summary table data. Then, based on the summary table data, a pre-formatted output file is generated. This transforms the traditionally manual and repetitive cross-page data collection action into a coherent, one-time operation process, which helps to improve the problem of low efficiency in cross-page table data processing.

[0008] In one possible implementation, at least one in-page interaction method further includes at least one of row selection operation and column selection operation.

[0009] Therefore, by further incorporating row and column selection operations into the available in-page interaction methods, users can not only select rectangular areas (box selection) but also select entire rows or columns that conform to the data logical structure when making selections across pages, thereby improving the flexibility and adaptability of the method to meet different data selection needs.

[0010] In one possible implementation, obtaining table data within a selected range for each of multiple pages includes: determining a row range and a column range selected by a first operation in at least one page; and extracting table data for at least one page from the underlying data model of the corresponding page based on the row range and column range.

[0011] Therefore, by directly extracting the original table data from the underlying data model based on the row and column range, the dependence on graphical interface elements is bypassed, which helps to improve the accuracy and completeness of the acquired data and provides a reliable data source for generating high-quality summary output.

[0012] In one possible implementation, obtaining summary table data based on table data within a selected range of each page includes: in response to a received second operation, determining the output method of the summary table data, wherein the second operation is a selection operation for determining the output method; and concatenating the table data within the selected range of each page to directly obtain the summary table data.

[0013] This limits the steps to first responding to the second operation of selecting the output method, and then directly concatenating the selected data from each page to obtain the summary table data. This provides a quick processing method of "first determine the format, then directly integrate and output," offering users a fast output channel without the need for preview confirmation, thus improving operational efficiency.

[0014] In one possible implementation, generating an output file in a predetermined format based on the summary table data includes: outputting the summary table data as an output file in a predetermined format based on the output method determined by the second operation.

[0015] Therefore, based on the quick determination of the output method, the summary table data can be generated into an output file of the corresponding format, thus completing the closed loop from format specification to file generation, which helps to achieve the integrity and executability of the fast output path.

[0016] In one possible implementation, before obtaining summary table data based on table data within a selected range of each page, and after obtaining table data within a selected range of each of the multiple pages in response to a received first operation, the method further includes: displaying a preview interface in response to a received third operation, wherein the third operation indicates previewing table data within a selected range of each page, the preview interface being used to present preview data generated by integrating table data within a selected range of each page.

[0017] Therefore, by providing a preview generated based on the initial selection data, users can intuitively review the overall effect of cross-page selections before the final output, which helps reduce errors caused by blind operation.

[0018] In one possible implementation, obtaining summary table data based on table data within a selected range of each page includes: in response to a fourth operation in the preview interface, determining the data range corresponding to the summary table data, wherein the fourth operation indicates modification of table data within a selected range of at least some of the multiple pages; and obtaining the summary table data based on the data range.

[0019] This limits the implementation method to determining the final output data range by receiving user operations (the fourth operation) in the preview interface. This allows users to modify and edit the initially selected pagination data based on the preview, such as including or excluding it, thereby achieving secondary correction before output and improving the accuracy of the output results.

[0020] In one possible implementation, generating an output file in a predetermined format based on summary table data includes: determining an output method for the summary table data in response to a fifth operation in the preview interface, wherein the fifth operation is a selection operation for determining the output method; and outputting the summary table data as an output file in a predetermined format based on the output method determined by the fifth operation.

[0021] Therefore, the implementation method is limited to determining the output method and generating the file by receiving user operations (the fifth operation) in the preview interface. This integrates the selection and confirmation of the output format within the preview editing path into the preview interface, allowing the complete "preview-edit-output" process to be completed within the same interface, thus optimizing the continuity of the interaction.

[0022] In one possible implementation, the predetermined format includes an image format or a text format.

[0023] Therefore, specifying the predetermined format of the output file into common image or text formats helps to directly apply the output results to practical scenarios such as reports and archives, thereby enhancing the practical value of the solution and broadening its application scope.

[0024] In one possible implementation, generating an output file in a predetermined format based on summary table data includes: converting the summary table data into an initial file in text format; using the initial file as a text format output file if the predetermined format is text format; and converting the initial file into an image format output file if the predetermined format is image format.

[0025] This provides a possible conversion process for generating image format files, offering a clear logical example for the implementation of the solution, and indirectly demonstrating the characteristics of image formats in terms of fixed content presentation (i.e., the content in the image is not easily tampered with).

[0026] Secondly, embodiments of this application provide a cross-page table data integration and output device, which includes:

[0027] The acquisition module is configured to, in response to a received first operation, acquire table data within a selected range of each of multiple pages, wherein the selected range of each of one or more pages represents a partial data area in the table of that page; the first operation includes a selection operation performed on at least two of the multiple pages switched through a navigation operation, selecting a selected range of at least one page using at least one in-page interaction method, wherein the one or more pages include at least one page; the at least one in-page interaction method includes a drag-based selection operation; the processing module is configured to obtain summary table data based on the table data within the selected range of each page; and the generation module is configured to generate an output file in a predetermined format based on the summary table data.

[0028] Optionally, the acquisition module specifically includes at least one of the following in-page interaction methods: row selection operation and column selection operation.

[0029] Optionally, the acquisition module is specifically used to determine the row range and column range selected by the first operation in at least one page; and to extract the table data of at least one page from the underlying data model of the corresponding page based on the row range and column range.

[0030] Optionally, the processing module is specifically used to, in response to the received second operation, determine the output method of the summary table data, wherein the second operation is a selection operation for determining the output method; and to concatenate the table data within the selected range of each page to directly obtain the summary table data.

[0031] Optionally, the generation module is specifically used to output the summary table data into an output file in a predetermined format based on the output method determined by the second operation.

[0032] Optionally, the processing module is further configured to, in response to a received third operation, display a preview interface before obtaining summary table data based on the table data within a selected range of each page, wherein the third operation indicates previewing the table data within a selected range of each page, and the preview interface is used to present preview data generated by integrating the table data within the selected range of each page.

[0033] Optionally, the processing module is specifically used to, in response to the fourth operation in the preview interface, determine the data range corresponding to the summary table data, wherein the fourth operation indicates the modification of the table data within the selected range of at least some of the multiple pages; and obtain the summary table data based on the data range.

[0034] Optionally, the processing module is specifically used to determine the output method of the summary table data in response to the fifth operation in the preview interface, wherein the fifth operation is a selection operation for determining the output method; the generation module is specifically used to output the summary table data into an output file of a predetermined format based on the output method determined by the fifth operation.

[0035] Optionally, the generation module specifically includes a predefined format, including image format or text format.

[0036] Optionally, the generation module is specifically used to convert the summary table data into an initial file in text format; if the predetermined format is text format, use the initial file as an output file in text format; if the predetermined format is image format, convert the initial file into an output file in image format.

[0037] Thirdly, embodiments of this application also provide an electronic device, which includes a processor and a memory, wherein the memory is used to store computer program instructions, and the processor is used to call the computer program instructions stored in the memory to enable the electronic device to implement the cross-page table data integration and output method as described in the first aspect of this application.

[0038] Fourthly, embodiments of this application also provide a computer-readable storage medium for storing computer program instructions that, when executed by a processor, implement the cross-page table data integration and output method as described in the first aspect of this application.

[0039] Fifthly, embodiments of this application also provide a computer program product comprising a computer program that, when executed by a processor, implements the cross-page table data integration and output method as described in the first aspect of this application. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 An application scenario diagram of the cross-page table data integration and output method provided in the embodiments of this application;

[0042] Figure 2 A flowchart illustrating a method for integrating and outputting cross-page table data according to an embodiment of this application;

[0043] Figure 3 for Figure 2 The illustrated embodiment provides a schematic diagram of the user's interaction process with the table data interface;

[0044] Figure 4 A flowchart illustrating a method for integrating and outputting cross-page table data, as provided in yet another embodiment of this application;

[0045] Figure 5 for Figure 4 The illustrated embodiment provides a schematic diagram of a user's interaction with a table data interface;

[0046] Figure 6 for Figure 4 The illustrated embodiment provides another method of user interaction with a table data interface;

[0047] Figure 7 for Figure 4 The illustrated embodiment provides a schematic diagram of one implementation of the second operation;

[0048] Figure 8 A flowchart illustrating a method for integrating and outputting cross-page table data, as provided in yet another embodiment of this application;

[0049] Figure 9 for Figure 8 The preview interface structure diagram provided in the embodiment shown is as follows;

[0050] Figure 10A schematic diagram of the structure of a cross-page table data integration and output device provided in another embodiment of this application;

[0051] Figure 11 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application.

[0052] Explanation of reference numerals in the attached figures:

[0053] 100-Controller; 110-Terminal; 500-Spanning table data integration and output device; 510-Acquisition module; 520-Processing module; 530-Generation module; 60-Electronic device; 61-Processor; 62-Memory; 63-Transceiver. Detailed Implementation

[0054] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0055] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0056] In modern data analysis and experimental data processing, users often need to extract specific data regions spanning multiple pages from large, paginated tables and integrate them into a complete report or supporting document. This requirement demands high efficiency and professional output. The core challenge lies in the software's ability to intelligently understand the user's selection intent across multiple discrete "pages" or "display ranges" and seamlessly reassemble these fragmented data pieces logically and visually into a cohesive whole. Traditional methods inherently face obstacles in understanding data structures, ensuring operational coherence across logical boundaries, and accurately capturing user intent.

[0057] In related technologies, manually taking paginated screenshots and then stitching them together relies entirely on manual labor, which is extremely inefficient and prone to errors. General-purpose long screenshot tools can only capture continuously scrolling pixels and cannot recognize or respond to the "pagination" business logic of tables. Therefore, they cannot support selective capture of non-continuous pages, nor can they provide preview and editing opportunities based on data structures before output, resulting in insufficient automation and controllability of results.

[0058] To address this issue, this application provides a method for integrating and outputting cross-page table data. By introducing a dedicated preview interface as a key hub, this interface pops up after the user completes the initial cross-page selection to centrally display the data integration preview and carry out the final confirmation operation. This integrates the originally discrete multiple steps into a controllable automated task, effectively overcoming the obstacles of fragmented operation and inaccurate intent transmission.

[0059] The following explains one possible application scenario of the embodiments of this application:

[0060] Figure 1 This diagram illustrates an application scenario of the cross-page table data integration and output method provided in this application. For example... Figure 1 As shown, in semiconductor photodetector, controller 100 acquires the interactive operation sent by the user through terminal 110, and integrates and outputs the selected table data based on the interactive operation.

[0061] It should be noted that, Figure 1 In the scenario shown, only one controller 100 and one terminal 110 are used as an example for illustration, but this application is not limited to this. That is to say, the number of controllers 100 and terminals 110 can be arbitrary.

[0062] It should be understood that this application scenario is only an example, and the application scenario can also be a daily office scenario, etc. The application scenario of this application is not limited here.

[0063] The following detailed embodiments illustrate the cross-page table data integration and output method provided in this application.

[0064] Example 1:

[0065] Figure 2 This is a flowchart illustrating a method for integrating and outputting cross-page table data according to an embodiment of this application. Figure 2 As shown, the cross-page table data integration and output method provided in this embodiment includes the following steps:

[0066] Step S201: In response to the received first operation, obtain table data within a selected range of each page in the multiple pages.

[0067] Wherein, the selected range of each page in one or more of the multiple pages is used to represent a portion of the data area in the table of that page; the first operation includes a selection operation performed on at least two of the multiple pages switched through the navigation operation, selecting the selected range of at least one page through at least one in-page interaction method, wherein the one or more pages (i.e., one or more pages in the multiple pages) include the at least one page; the at least one in-page interaction method includes a drag-based selection operation.

[0068] Specifically, in this application's embodiments, the executing entity is a system, service, process, processor, or other device running on the user's terminal device capable of performing table data integration and output (e.g., the terminal device is...). Figure 1 The term "system" refers to, for example, a data post-processing software system running on an industrial computer, or a built-in processor of a test and measurement instrument that integrates this function.

[0069] As some implementation methods, this method can be applied to measurement and testing equipment, such as processing spot data analysis tables output by semiconductor measurement and testing equipment, or traffic statistics tables generated by network performance testers.

[0070] In this embodiment, the system runs on the user's terminal device, and its graphical interface displays data from testing equipment, detection equipment, databases or files in tabular form.

[0071] Due to the large volume of data, the table employs a pagination display mechanism. Here, "pagination" is a logical concept; for example, it can include classic pagination where users switch between pages by clicking page numbers or tabs; or it can include different visible areas presented sequentially when browsing an extremely long or wide table using vertical or horizontal scrollbars. Therefore, the system needs to understand and respond to the user's continuous selection intent across these logical boundaries.

[0072] Specifically, when a user begins to interact with the form, the system continuously listens for specific input events.

[0073] Here, the first operation is the user's interactive action of selecting across pages. The core of this is that the user switches between different display areas (i.e., pages) through navigation operations (such as clicking the pagination bar or dragging the scroll bar), and within at least two of the switched pages, performs a selection operation through at least one in-page interaction method. In this embodiment, the in-page interaction methods at least include drag-based selection.

[0074] For example, such as Figure 3 As shown, this is a schematic diagram illustrating the interaction process between a user and a table data interface provided in an embodiment of this application. The user may first appear on the current page (see reference...) Figure 3 As shown in (a) above, the display area is columns A to F and rows 1 to 6 on page 1. A rectangular area was selected by dragging the mouse, covering columns B to C and rows 2 to 5 (see reference). Figure 3(as shown in (c)). The system will immediately record this selected range, and its data structure may include: current page identifier (e.g., page 1), starting row number (2), ending row number (5), starting column number (B), and ending column number (C), which can be represented in the form of {1,2,5,B,C}.

[0075] Subsequently, the user can switch the interface to another display area by navigating (such as clicking the "Next Page" button or dragging the scroll bar) (see reference). Figure 3 As shown in (b) above, the display range is columns A to F and rows 1 to 6 on page 2. Within this display range, the user may have further selected columns C to E and rows 2 to 5 by holding down the Ctrl key and clicking the row header (see reference). Figure 3 (As shown in (d)). The system will recognize this as a new operation context and append this new selected range (which can be in the form of {2,2,5,C,E}) as a separate record, rather than overwriting the previous record.

[0076] The core principle behind the system's recording of these selected ranges is to transform the user's continuous, discrete sequences of operations on the interface into a set of structured selection instructions bound to the coordinates of the underlying data model. Its applications are very broad; for example, in semiconductor product defect detection, users need to extract abnormal data columns (distributed across multiple pages) from hundreds of pages of inspection results for comparative analysis.

[0077] In this way, the system accurately captures the two key dimensions of user intent: "cross-page" and "specific area," laying the foundation for subsequent processing.

[0078] In some embodiments, to achieve a better experience, the system can dynamically display the total amount and distribution of selected data at the edge of the interface in the form of floating prompts or mini-maps, so that users can have a clear sense of the operation progress.

[0079] Step S202: Based on the table data within the selected range of each page, obtain the summary table data.

[0080] Specifically, after a user completes the selection of data across multiple pages, the data needs to be integrated to obtain a complete summary table. Different implementation methods exist depending on the user interaction flow.

[0081] The system supports a variety of flexible and intuitive ways to trigger output operations, adapting to different users' operating habits and the current interface context.

[0082] In one implementation, after obtaining the selected range, the system directly concatenates the table data from each page in memory according to the logical order of the selected range (such as page order or row number order), thereby directly obtaining the summary table data. This path does not require an additional user confirmation interface and is designed to generate results quickly.

[0083] For example, such as Figure 3 As shown in (d) above, one approach is as follows: when a user right-clicks anywhere in the table area, the system detects the existence of a recorded selection range and dynamically generates an option, such as "Integrate Output," in the pop-up context menu. Clicking this menu item triggers the output process.

[0084] Another approach is to provide a persistent, clearly labeled physical button (a fixed interface control) at the top of the application window's toolbar or table control, such as a "Merge Screenshots" button. When the user selects this button, it changes from disabled to enabled, indicating that the user can perform the action.

[0085] In addition, the system can also support keyboard shortcuts, such as Ctrl+G (or other shortcut combinations), as a quick trigger channel.

[0086] In scenarios that prioritize immersive operation, the system can also display a semi-transparent floating button (interface floating control) fading into the corner of the screen after the user completes a selection, serving as a lightweight trigger prompt.

[0087] Subsequently, the system will extract the corresponding data from the underlying data model based on the range selected by the user when triggering the operation, and reassemble it in memory to obtain the final summary table data.

[0088] It should be noted that the underlying data model mentioned in the embodiments of this application refers to the structured data set and its logical relationships that drive the display and interaction of tables in the graphical interface. This includes the original, programmable representation of all data content, data types, data relationships, and potentially associated style attributes in the table. In practical applications, the underlying data model can exist in the form of internal program data structures (such as objects, arrays, lists), database record sets, or standardized data formats (such as JSON, XML) accessed through application programming interfaces (APIs).

[0089] For example, such as Figure 3 The underlying data model corresponding to the table data shown in (a) can be represented as follows:

[0090] {1, Zhang Yi, 100, 0, empty, 0}, {2, Zhang Er, 100, 0, empty, 0}, {3, Zhang San, 100, 0, empty, 0}, {4, Zhang Si, 100, 0, empty, 0}, {5, Zhang Wu, 100, 0, empty, 0}, {6, Zhang Liu, 100, 0, empty, 0}…

[0091] Each row in the table can be represented by an array structure within curly braces {}, thus obtaining the underlying data model representing the data in the entire "Page 1".

[0092] Step S303: Generate an output file in a predetermined format based on the summary table data.

[0093] Specifically, after obtaining the summary table data, the system calls the corresponding processing module to generate the final file according to the output method specified by the user (such as specifying it through default settings or previous shortcut operations in "Direct Output Path"; or selecting it in the preview interface in "Preview Edit Path").

[0094] For example, if the output is in image format, the system can use the open-source Canvas library to render the summary table data as a PNG or JPEG image; if it's in PDF format, it will call a PDF generation library for layout generation; if it's in Excel format, it will generate an .xlsx file. In this case, the output table can be displayed as follows: Figure 3 As shown in (e). After processing is complete, the system triggers file download or saving, completing the entire output process.

[0095] The cross-page table data integration and output method provided in this application embodiment acquires data by responding to user selection operations across multiple pages, then integrates the data to obtain a summary data and generates a file. This integrates the traditional manual pagination process into an automated workflow, which helps improve the efficiency of cross-page table data processing and reduces the possibility of errors caused by tedious operations. In other words, by limiting the process to at least two pages switched through navigation operations, users can freely specify all or part of the data area of ​​each page through page-interactive methods such as selection and integrate it to obtain summary table data. Then, based on the summary table data, an output file in a predetermined format is generated. This transforms the traditionally manual and repetitive cross-page data acquisition action into a coherent, one-time operation process, which helps to improve the problem of low efficiency in cross-page table data processing.

[0096] Example 2:

[0097] Figure 4 This is a flowchart illustrating a method for integrating and outputting cross-page table data according to an embodiment of this application. Figure 4 As shown, the cross-page table data integration and output method provided in this embodiment is used for... Figure 2Based on the illustrated embodiment, a further description is provided of an implementation method for integrating and outputting cross-page table data, which includes the following steps:

[0098] Step S301: In response to the received first operation, determine the row range and column range selected by the first operation in at least one page.

[0099] Specifically, the first operation is to determine the table data to be integrated and output, which is the cross-page data selection operation performed by the user in the graphical interface. Therefore, when the first operation is received, the system needs to determine the corresponding data range, including the page number range, row range, column range, etc.

[0100] During the specific interaction, users navigate using actions such as clicking the pagination tool (see reference). Figure 3 The controls (such as "Page 1", "Page 2", "Page 3", etc.) allow switching between different pages, and the program should be able to navigate between at least two pages (e.g., ...). Figure 3 (Page 1 and Page 2) Select data through in-page interactions.

[0101] The specific in-page interaction method in the first operation can be a drag-and-drop selection operation. The system binds mouse event listeners to cells and records the cell coordinates when the mouse is pressed and released, thereby determining the start and end row and column indices of the selected area, and thus obtaining the row range and column range. For relevant details, please refer to the corresponding description in Example 1, which will not be repeated here.

[0102] In addition, at least one in-page interaction method includes at least one of the following: row selection operation and column selection operation.

[0103] like Figure 5 The diagram shown illustrates a user interaction method with a table data interface according to an embodiment of this application. Figure 5 Row selection operations (e.g.) Figure 5 (a) in the example, i.e., selecting rows 2 and 5) and column selection operations (such as... Figure 5 (b) refers to selecting columns B and D. At this point, the user can directly select the row or column headers (e.g., by clicking...). Figure 5 In columns B and D, or by selecting the selection control to the left of the cells containing the numbers 2 and 5 in column A. Figure 5 By selecting the two checkboxes, you can directly select the entire column or row, enabling row and column selection operations.

[0104] In some implementations, the system provides richer visual feedback when a user makes a selection across pages. For example, when a user holds down the Ctrl key and clicks the top of a table row, in addition to highlighting that row, a checkmark icon (e.g., ...) can be persistently displayed at the top of the row. Figure 5The checkbox in (a) clearly indicates that the row has been included in the selection range until the user actively deselects it.

[0105] In some implementations, the system provides different row selection interaction modes. In a mode called "partial selection mode," the user holds down the Ctrl key and clicks the top of a row to select only the currently displayed columns. In "select all mode," the same operation will automatically select all data columns in the row (including columns that may not be displayed due to scrolling). Users can select the currently active mode using the mode toggle button on the interface.

[0106] In some embodiments, the in-page interaction methods may also include a select all operation, such as... Figure 6 As shown, this is a schematic diagram of another interaction method between a user and a table data interface provided in an embodiment of this application. Figure 6 In the table interface, there is a control in the upper left corner (i.e. Figure 6 The control is located in the top left corner of the table interface. Clicking this control allows you to select all data on that page. In practice, you can also achieve the same selection operation using other controls or keyboard shortcuts (such as Ctrl+A) provided by the software interface.

[0107] In addition to in-page interaction methods, it also includes navigation operations for switching pages, as described in Example 1.

[0108] Based on the above method, the system can determine the range corresponding to all table data specified by the user, that is, the selected range.

[0109] Step S302: Extract at least one page of table data from the underlying data model of the corresponding page based on the row range and column range.

[0110] Specifically, based on the structured coordinates (row range, column range) determined in step S301, the system can directly access the underlying data model supporting table rendering (such as a dataset array in memory or database query results), extract the corresponding original data units and their style information (font, color, etc.), and improve the accuracy and fidelity of the data.

[0111] Step S303: In response to the received second operation, determine the output method of the summary table data.

[0112] The second operation is a selection operation used to determine the output method.

[0113] Specifically, after a user completes the cross-page data selection, there's no need to enter a dedicated preview interface; the output process can be triggered directly within the original operation context (i.e., the main interface where the table is located). The second operation here is the user-issued instruction to directly specify the output method.

[0114] In terms of specific implementation, it can be as follows: Figure 7 The diagram illustrates one implementation of the second operation. Users can invoke a context menu item to perform the second operation. Specifically, users can right-click within the table area. After detecting a selected range of records, the system provides a "Consolidate Output" option in the right-click menu. When the user selects this option, a secondary menu appears to the right, such as "Direct Output as Table" or "Direct Output as Image." Clicking on one of these options completes the selection of the output method (the second operation).

[0115] In practical applications, fixed or floating controls can also be provided in the table interface. When the user clicks a preset button on the main interface toolbar that represents a specific format, the click action is treated as a second operation.

[0116] Alternatively, preset shortcut keys can be provided. For example, when a user presses Ctrl+Shift+E (corresponding to exporting Excel), the system recognizes this shortcut key event as a second operation and determines the corresponding output method.

[0117] Step S304: Combine the table data within the selected range of each page to directly obtain the summary table data.

[0118] Specifically, after receiving the second operation and specifying the output method, the system immediately initiates the data processing flow. Based on the table data fragments extracted from each page in step S302, the system splices and reassembles them in memory according to their logical order in the original table (such as page order, row numbers, and column numbers) to generate a logically complete and continuous summary table data object. This process is automated, without any intermediate user intervention.

[0119] Step S305: Based on the output method determined in the second operation, output the summary table data into an output file with a predetermined format.

[0120] Specifically, based on the output method determined in step S303, the system calls the corresponding backend processing module to convert the summary table data obtained in step S304 into a file in the target format.

[0121] If the output is an image, the system can use open-source libraries such as html-to-image to render the summary table data onto an off-screen Canvas and encode it as an image file; if the output is a table file, libraries such as SheetJS may be used to generate an .xlsx format file.

[0122] After the file is generated, the system automatically triggers the browser's download process or saves the file to a specified location, thus completing a "one-click" direct operation from cross-page selection to final file output.

[0123] The cross-page table data integration and output method provided in this embodiment achieves a fast output path without the need for preview confirmation by directly responding to the output method selection operation (second operation) on the main interface and automatically completing data concatenation and format conversion. This helps meet the needs of application scenarios with extreme requirements for operational efficiency and improves the convenience of cross-page table data processing.

[0124] Example 3:

[0125] Figure 8 This is a flowchart illustrating a method for integrating and outputting cross-page table data according to an embodiment of this application. Figure 8 As shown, the cross-page table data integration and output method provided in this embodiment is used for... Figure 2 and Figure 4 Based on the illustrated embodiment, another implementation method for integrating and outputting cross-page table data is further described, which includes the following steps:

[0126] Step S401: In response to the received first operation, obtain table data within a selected range of each page in the multiple pages.

[0127] Specifically, in this embodiment, after the user determines the selected range of the table data to be output through the first operation, the user can complete the subsequent integration and output actions by triggering the preview interface, which will be described in detail below.

[0128] Step S402: In response to the received third operation, display the preview interface.

[0129] The third operation indicates that the table data within the selected range of each page is previewed. The preview interface is used to present preview data generated by integrating the table data within the selected range of each page.

[0130] Specifically, after a user completes a cross-page selection, the preview process is triggered through a specific action (the third operation). This third operation can be clicking the "Preview" option in the right-click menu, clicking the "Preview" button in the toolbar, or using a specific keyboard shortcut. For example... Figure 7 In the middle, select the "Output Preview" option from the secondary menu that pops up in the right-click menu to open the preview interface.

[0131] like Figure 9 The diagram shown illustrates the preview interface structure. The preview interface includes: a data preview area, a selection / editing area, and an output settings area.

[0132] The data preview area dynamically displays the overall table effect after initial integration based on the currently selected range. Figure 9 The table section.

[0133] In the selection editing area, the relevant pages are displayed in a list format (e.g., "Page 1", "Page 2"), with a checkbox next to each list item. Figure 9 As shown, the user's actions in this area constitute a subsequent edit of the output data range (i.e., the fourth action).

[0134] The output settings area provides output format options such as "Copy to clipboard" and "Export as image". Figure 9 As shown in the image.

[0135] In some embodiments, in the selection and editing area of ​​the preview interface, the system not only displays the pagination list but also related data statistics. For example, next to the "Page 1" entry, in addition to the checkbox, text such as "10 / 20, Total: 200, Selected: 10, Total selected: 150" can be displayed. Figure 9 (Not shown in the image). "10 / 20" indicates there are 10 pages of data, with 20 rows per page. "Total: 200" indicates a total of 200 rows across all pages (i.e., 10 * 20). "Selected: 10" indicates 10 rows are selected on the current page. "Total selected: 150" indicates a total of 150 selected rows across all pages. This method visually displays the total number of data rows and the selection status, helping users make informed decisions.

[0136] Step S403: In response to the fourth operation in the preview interface, determine the data range corresponding to the summary table data.

[0137] The fourth operation indicates the modification of table data within a selected range of at least some of the multiple pages.

[0138] Specifically, users can perform operations in the selection and editing area of ​​the preview interface, such as unchecking the checkbox for a specific page to exclude all data on that page (e.g., ...). Figure 9 In the middle, that is, the checkboxes corresponding to page 1 and page 2 are checked.

[0139] In response to this fourth operation, the system will update the set of valid data ranges to be integrated and output.

[0140] Meanwhile, the data preview area will be updated in real time to reflect the edited data content and provide users with immediate feedback.

[0141] In some embodiments, the preview interface supports progressively deeper editing of pagination data. Users can click on a page number in the pagination list, and the system will then display, either in the main area of ​​the interface or in a new window, all the rows and columns that have been initially selected for that page (e.g., ...). Figure 9 In the view, clicking the "Page 1" option will highlight the corresponding data on the first page. Each row or column in this view has checkboxes next to it, allowing users to precisely control the subset of rows and columns in the final output of that page by checking or dechecking them, enabling fine-grained page-level editing.

[0142] Step S404: Based on the data range, obtain the summary table data.

[0143] Specifically, based on the determined final data range, the system will initiate a backend data processing flow to generate logically complete summary table data.

[0144] During this process, the system extracts data units from the underlying data model, including directly accessing the underlying data model that drives the table (such as a JSON dataset), and extracting the original data and its complete style (font, color, merging attributes, etc.) based on the pagination identifier and cell coordinates specified by the data range.

[0145] Subsequently, the system reassembles the data into a logically complete set. By recalculating and arranging the data "fragments" extracted from different pages in memory according to their original row and column indexes, the system can construct a new, continuous structured data object and correctly handle complex styles such as cell merging, thereby improving the fidelity of the table structure.

[0146] In some embodiments, the system can also perform intelligent optimization during the data processing phase. When generating summary table data based on the finally determined data range, the system checks the content of all cells column by column. If a column is found to contain only empty values ​​or placeholders in all rows, it will be automatically ignored before output, thereby generating a more compact and information-dense output file.

[0147] Step S405: In response to the fifth operation in the preview interface, determine the output method of the summary table data.

[0148] The fifth operation is a selection operation used to determine the output method.

[0149] Specifically, in the output settings area of ​​the preview interface, the user selects the desired final file format (e.g., ...). Figure 9 In the middle, the "Copy to Clipboard" button was selected. This selection action is the fifth operation, which clarifies the specific format of the subsequently generated file.

[0150] Step S406: Based on the output method determined in the fifth operation, output the summary table data into an output file with a predetermined format.

[0151] Specifically, the system calls the dedicated processing module corresponding to the selected output method to convert the summary table data obtained in step S404 into the target format file.

[0152] In practice, if the output is an image, the system will call open-source libraries such as html-to-image or Canvas to render the data to an off-screen canvas and encode it as a PNG / JPEG image; if the output is a PDF, the system can call libraries such as jsPDF to format the data according to page rules and generate a PDF document; if the output is a table, the system can call libraries such as SheetJS to generate .xlsx or .xls format files; if the output method is copy to the clipboard, the system can convert the data into rich text or HTML format and write it through the browser's Clipboard API.

[0153] Once processing is complete, the system triggers a file download or save operation, thus completing the entire "preview-edit-output" process.

[0154] In some embodiments of this application, the predetermined format includes image format or text format.

[0155] Specifically, the output formats are usually image and text formats. The image formats referred to here are file formats that store visual information in the form of pixel raster or vector graphics, such as PNG, JPEG, and PDF. The text formats referred to here are file formats that mainly contain encoded character sequences, can be directly read and edited by text editors, or can be parsed into structured data by specific applications, such as CSV, EXCEL, and plain text formats (such as .txt text documents).

[0156] It's important to note that classifying PDFs as image formats is based on their core purpose of providing fixed, non-editable visual output; while classifying Excel as a text format is based on its core characteristic of providing structured data and supporting direct editing. This classification helps in understanding the different application scenarios emphasized by each output format.

[0157] Depending on the actual characteristics, the classification can also be adjusted, such as classifying PDF as a text format.

[0158] At this point, the method for generating an output file in a predetermined format specifically includes:

[0159] Step A1: Convert the summary table data into an initial file in text format.

[0160] Specifically, during output, the system first serializes the structured summary table data object in memory into a generic, style-independent plain text representation, such as a CSV file.

[0161] At this point, the system iterates through each row of the summary table data, extracting the text content of each cell in the row. To prevent formatting errors caused by commas or line breaks in the cell content itself, the system encloses each field in double quotes. After each row of data is extracted, all fields in that row are connected using a predefined delimiter (such as a comma), and a line break is added at the end of the row. Finally, all rows are concatenated to form a complete CSV format string, which is the initial text file.

[0162] Another approach is to generate plain text tables that maintain simple alignment. The system needs to calculate the maximum character width of each column and add appropriate spaces when filling cell content to achieve visual column alignment.

[0163] Step A2: If the predetermined format is text, use the initial file as the output file in text format.

[0164] Specifically, when the user selects a text format (such as CSV or TXT), the initial file generated in step A1 is already the final required output format. The system will encapsulate this text string (or byte stream) into a standard file object for output.

[0165] Step A3: If the predetermined format is image format, convert the initial file into an image format output file.

[0166] Specifically, when the predetermined format is an image (such as PNG or JPEG), the system needs to convert the initial file content in text form into a pixel image, rather than directly processing the original summary table data.

[0167] This conversion does not directly encode the text file, but rather re-renders its visual content. One feasible implementation is: the system first parses the initial text file generated in step A1, and reloads its data content into a temporary, invisible HTML table element (…).

[0168]

[0169]

[0170]

[0171]

[0172] Figure 10 Figure 10

[0173]

[0174]

[0175]

[0176]

[0177]

[0178]

[0179]

[0180]

[0181]

[0182]

[0183]

[0184]

[0185]

[0186]

[0187] Figure 11 Figure 10

[0188]

[0189]

[0190]

[0191]

[0192] Figure 10

[0193]

[0194]

[0195]

[0196]

[0197]

[0198]

[0199]

[0200]

[0201]

[0202]

[0203]

[0204] In this process, the system needs to restore or apply basic table styles (such as font, background color, borders, etc.) from the original summary table data object to this temporary table. Next, using an open-source library (such as html2canvas) or a Canvas-based API, the rendered temporary table elements are drawn onto an off-screen Canvas. The drawing process precisely converts HTML / CSS styles into bitmap pixels. Finally, the Canvas's toDataURL() or toBlob() methods are called, specifying the image format (such as image / png) and optional quality parameters, encoding the canvas content into image binary data (Blob object), and generating the final image format output file by triggering a download. The cross-page table data integration and output method provided in this embodiment introduces a preview interface, allowing users to visually review the integration effect of cross-page selected data before output, and directly edit the final output range by checking / unchecking pagination, with the preview updating in real time. Subsequently, the system extracts and reassembles data from the underlying data model, improving the high fidelity of the output. After the user confirms the output format in the preview interface, the system automatically converts it to an image or text file. This provides users with a complete and controllable process from previewing and correction to output, solving the problem of not being able to preview the entire page and easily correct cross-page data in traditional methods, and significantly improving the user experience and the accuracy of the results. Example 4: A schematic diagram of the structure of a cross-page table data integration and output device provided in one embodiment of this application. As shown, the cross-page table data integration and output device 500 includes: an acquisition module 510, a processing module 520, and a generation module 530. The acquisition module 510 is used to acquire table data within a selected range of each page in a plurality of pages in response to a received first operation, wherein the selected range of each page in one or more pages in the plurality of pages is used to represent a partial data area in the table of that page; the first operation includes a selection operation performed by at least one in-page interaction method on at least two pages in a plurality of pages switched through a navigation operation, selecting the selected range of at least one page, wherein the one or more pages include at least one page; the at least one in-page interaction method includes a drag-based selection operation. The processing module 520 is used to obtain summary table data based on the table data within the selected range of each page. The generation module 530 is used to generate an output file in a predetermined format based on the summary table data. Optionally, the acquisition module 510 specifically includes at least one of row selection operation and column selection operation in at least one page interaction method. Optionally, the acquisition module 510 is specifically used to determine the row range and column range selected by the first operation in at least one page; and extract the table data of at least one page from the underlying data model of the corresponding page based on the row range and column range.Optionally, the processing module 520 is specifically used to, in response to the received second operation, determine the output method of the summary table data, wherein the second operation is a selection operation for determining the output method; and concatenate the table data within the selected range of each page to directly obtain the summary table data. Optionally, the generation module 530 is specifically used to, based on the output method determined by the second operation, output the summary table data as an output file in a predetermined format. Optionally, the processing module 520 is further used to, before obtaining the summary table data based on the table data within the selected range of each page, in response to the received third operation, display a preview interface, wherein the third operation indicates previewing the table data within the selected range of each page, and the preview interface is used to present preview data generated by integrating the table data within the selected range of each page. Optionally, the processing module 520 is specifically used to, in response to a fourth operation in the preview interface, determine the data range corresponding to the summary table data, wherein the fourth operation indicates modification of the table data within the selected range of at least some pages in multiple pages; and obtain the summary table data based on the data range. Optionally, the processing module 520 is specifically used to determine the output method of the summary table data in response to the fifth operation in the preview interface, wherein the fifth operation is a selection operation for determining the output method; the generation module 530 is specifically used to output the summary table data into an output file of a predetermined format based on the output method determined by the fifth operation. Optionally, the generation module 530 specifically includes a predetermined format including an image format or a text format. Optionally, the generation module 530 is specifically used to convert the summary table data into an initial file in text format; if the predetermined format is text format, use the initial file as a text format output file; if the predetermined format is image format, convert the initial file into an image format output file. It should be understood that the effects of the operations performed by each module can be seen from the foregoing and will not be repeated here. In this embodiment, the cross-page table data integration and output device solves the problem of cumbersome and error-prone operation of cross-page table data integration and output in related technologies by combining the various modules. This is a schematic structural diagram of the electronic device provided in this application. The electronic device 60 includes a processor 61 and a memory 62. The processor 61 is coupled to the memory 62, which stores computer programs or instructions and / or data. The processor 61 executes / calls the computer programs or instructions stored in the memory 62, or reads the data stored in the memory 62, so that the electronic device 60 performs the methods in the above-described method embodiments. For example, the electronic device 60 incorporates a cross-page table data integration output device 500 as shown. Optionally, there may be one or more processors 61. Optionally, there may be one or more memories 62. Optionally, the memory 62 may be integrated with the processor 61, or may be separately disposed. Optionally, the electronic device 60 also includes a transceiver 63 for receiving and / or transmitting signals.For example, processor 61 is used to control transceiver 63 to receive and / or transmit signals. It should be noted that each of the above modules or units can be implemented in software, hardware, or a combination of both. For example, as shown, when the processor 61 of electronic device 60 is a CPU, the above-mentioned acquisition module 510, processing module 520, and generation module 530 can all be implemented in software. In this application, "implemented in software" means that the processor (e.g., processor 61) reads and executes program instructions stored in memory (e.g., memory 62) to implement the functions corresponding to the above-mentioned modules or units. Here, a processor refers to a processing circuit capable of executing program instructions, including but not limited to at least one of the following: CPU, microprocessor, digital signal processor (DSP), microcontroller unit (MCU), or artificial intelligence processor, etc., and other processing circuits capable of running program instructions. In other embodiments, the processor may also include circuits with other processing functions (such as hardware circuits for hardware acceleration, bus and interface circuits, etc.). Processors can be presented as integrated chips, for example, as integrated chips whose processing function only includes executing software instructions, or as SoCs (system on a chip), that is, a single chip including processing circuits capable of running program instructions (usually called "cores") as well as other hardware circuits for implementing specific functions (of course, these hardware circuits can also be implemented separately based on ASICs or FPGAs). Correspondingly, the processing function includes not only executing software instructions but also various hardware acceleration functions (such as AI calculations, encoding / decoding, compression / decompression, etc.). In this application, "implemented in hardware" means that the functions of the above modules or units are implemented through hardware processing circuits that do not have program instruction processing functions. These hardware processing circuits can be composed of discrete hardware components or integrated circuits. To reduce power consumption and size, integrated circuits are usually used. The hardware processing circuits can include ASICs or PLDs (programmable logic devices); among which, PLDs can include FPGAs, CPLDs (complex programmable logic devices), etc.These hardware processing circuits can be a single packaged semiconductor chip (e.g., packaged as an ASIC); or they can be integrated with other circuits (e.g., CPU, DSP) and packaged into a single semiconductor chip. For example, multiple hardware circuits and a CPU can be formed on a silicon substrate and packaged into a single chip, also known as a SoC. Alternatively, circuits for implementing FPGA functions and a CPU can be formed on a silicon substrate and packaged into a single chip, also known as a SoPC (system on a programmable chip). It should be noted that this application, when implemented through software, hardware, or a combination of both, can use different software or hardware, and is not limited to using only one type. For example, one module or unit can be implemented using a CPU, while another can be implemented using a DSP. Similarly, when implemented using hardware, one module or unit can be implemented using an ASIC, while another can be implemented using an FPGA. Of course, it is not limited to using the same software (e.g., all through a CPU) or the same hardware (e.g., all through an ASIC) to implement some or all modules or units. Furthermore, those skilled in the art will understand that software is generally more flexible but less performant than hardware, while hardware is the opposite. Therefore, those skilled in the art can choose software, hardware, or a combination of both based on actual needs. Additionally, this application provides a computer-readable storage medium storing computer program instructions. When these instructions are executed by a processor, they implement the methods in the various method embodiments of this application. For example, the processor is a computer processor. This application also provides a computer program product comprising a computer program. When the computer program is executed by a processor, it implements the methods in the various method embodiments of this application. For example, the computer program may take the form of program code, program instructions, etc. Furthermore, this application provides a chip including a processor. A memory for storing the computer program is provided independently of the chip, and the processor executes the computer program stored in the memory to execute the methods in the various method embodiments of this application. Further, the chip may also include a communication interface. The communication interface may be an input / output interface or an interface circuit, etc. Further, the chip may also include a memory. It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with the ability to process signals. In the implementation process, each step of the above method embodiment can be completed by the integrated logic circuit in the processor hardware or by software instructions.The processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly implemented by a hardware encoding processor, or implemented by a combination of hardware and software modules in the encoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. The memory in this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), and synchronous link dynamic memory (SLDRAM). It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory can be integrated into the processor.It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory. The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for integrating and outputting cross-page table data, characterized in that, The method includes: In response to a received first operation, table data within a selected range of each of the multiple pages is retrieved, wherein the selected range of one or more of the multiple pages represents a partial data area in the table of that page; the first operation includes a selection operation performed on at least two of the multiple pages switched through a navigation operation, selecting a selected range of at least one page using at least one in-page interaction method, wherein the one or more pages include the at least one page; the at least one in-page interaction method includes a drag-based selection operation; In response to the received second operation, the output method of the summary table data is determined, wherein the second operation is a selection operation for determining the output method; The table data within the selected range of each page is concatenated to directly obtain the summary table data, and the summary table data is output as an output file in a predetermined format based on the output method determined by the second operation. In response to a received third operation, a preview interface is displayed, wherein the third operation indicates previewing the table data within a selected range of each page. The preview interface includes: a data preview area, a selection editing area, and an output settings area. The data preview area is used to present preview data generated by integrating the table data within the selected range of each page. The selection editing area is used to display the pages involved in the selected range as list items, and each list item is configured with a checkbox. When a page in the involved pages is clicked, the corresponding data on that page is highlighted. The output settings area includes output format options. In response to a fourth operation on the checkbox, a data range corresponding to the summary table data is determined, and summary table data is obtained based on the data range; wherein the fourth operation indicates modification of table data within a selected range of at least a portion of the plurality of pages; In response to a fifth operation in the output settings area, the output method of the summary table data is determined, and based on the output method determined by the fifth operation, the summary table data is output as an output file in a predetermined format; wherein, the fifth operation is a selection operation for determining the output method; The predetermined format includes image format or text format; When the interaction method within the page is a drag-and-drop selection operation, obtaining the table data within the selected range of each page in multiple paginations includes: Determine the row and column ranges selected by the first operation within the at least one page; the row and column ranges are determined based on the cell coordinates corresponding to the first operation; Based on the coordinates corresponding to the row and column ranges, extract the table data of at least one page from the underlying data model of the corresponding page.

2. The method according to claim 1, characterized in that, The at least one in-page interaction method also includes: At least one of row selection operation and column selection operation.

3. The method according to claim 1, characterized in that, The step of outputting the summary table data into an output file of a predetermined format includes: Convert the summary table data into an initial file in the text format; When the predetermined format is the text format, the initial file is used as the output file in the text format; If the predetermined format is the image format, the initial file is converted into an output file in the image format.

4. A device for integrating and outputting cross-page table data, characterized in that, The device includes: The acquisition module is configured to, in response to a received first operation, acquire table data within a selected range of each of a plurality of pages, wherein the selected range of each of one or more of the plurality of pages represents a partial data area in the table of that page; the first operation includes a selection operation performed on at least two of the plurality of pages switched through a navigation operation, selecting a selected range of at least one page through at least one in-page interaction method, wherein the one or more pages include the at least one page; the at least one in-page interaction method includes a drag-based selection operation; The processing module is configured to, in response to a received second operation, determine the output method of the summary table data, wherein the second operation is a selection operation for determining the output method; The table data within the selected range of each page is concatenated to directly obtain the summary table data; The generation module is used to output the summary table data into an output file with a predetermined format based on the output method determined by the second operation; The processing module is further configured to respond to a received third operation by displaying a preview interface, wherein the third operation indicates previewing table data within a selected range of each page. The preview interface includes a data preview area, a selection editing area, and an output settings area. The data preview area is used to present preview data generated by integrating table data within a selected range of each page. The selection editing area is used to display the pages involved in the selected range as list items, each list item being configured with a checkbox. When a page in the involved pages is clicked, the corresponding data on that page is highlighted. The output settings area includes output format options. In response to a fourth operation on the checkbox, a data range corresponding to the summary table data is determined, and summary table data is obtained based on the data range; wherein the fourth operation indicates modification of table data within a selected range of at least a portion of the plurality of pages; In response to the fifth operation in the output settings area, the output method of the summary table data is determined; The generation module is further configured to output the summary table data into an output file of a predetermined format based on the output method determined by the fifth operation; wherein, the fifth operation is a selection operation for determining the output method; The predetermined format includes image format or text format; When the interaction method within the page is a drag-and-drop selection operation, the acquisition module is specifically used to determine the row range and column range selected by the first operation in the at least one page; the row range and the column range are determined based on the cell coordinates corresponding to the first operation; Based on the coordinates corresponding to the row and column ranges, extract the table data of at least one page from the underlying data model of the corresponding page.

5. An electronic device, characterized in that, include: A processor and a memory, the memory being used to store computer program instructions, the processor being used to invoke the computer program instructions stored in the memory to cause the electronic device to implement the cross-page table data integration and output method according to any one of claims 1 to 3.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store computer program instructions that, when executed by a processor, implement the cross-page table data integration and output method according to any one of claims 1 to 3.

7. A computer program product, characterized in that, The method includes a computer program, wherein when the computer program is executed by a processor, it implements the cross-page table data integration and output method according to any one of claims 1 to 3.

Images