Meeting layout methods and devices

Abstract

This application discloses a meeting layout method and apparatus. The meeting layout method includes: entering a custom layout interface; deleting a corresponding display cell in the custom layout interface in response to a first instruction; and deleting the display window of the corresponding display cell in the custom layout interface in response to a second instruction. The first instruction and the second instruction correspond to different types of instruction actions. Based on this method, accidental deletion can be effectively avoided, improving the reliability of the meeting layout method.

Description

Technical Field

[0001] This application relates to the field of online conferencing technology, and in particular to conferencing setup methods and apparatus. Background Technology

[0002] In existing technologies, online meetings display the meeting interface according to a pre-set meeting layout. This layout typically includes several subdivisions, each representing a specific area for displaying different content. When adjusting the current or preset meeting layout, it is often necessary to delete some subdivisions and their corresponding display windows to remove redundant or incorrectly displayed windows.

[0003] The drawback of existing technologies is that current layout methods typically require users to click buttons to delete cells and display windows. This means that each cell and display window has a separate delete button, which makes it easy for users to accidentally delete the cell containing the display window when deleting it. As a result, users have to add the accidentally deleted cell back in. Therefore, the reliability of existing meeting layout methods is poor. Summary of the Invention

[0004] The main technical problem addressed in this application is how to improve the reliability of meeting layout methods.

[0005] To solve the above-mentioned technical problems, the first technical solution adopted in this application is: a meeting layout method, including: entering a custom layout interface; deleting the corresponding display cell in the custom layout interface in response to a first instruction; and deleting the display window of the corresponding display cell in the custom layout interface in response to a second instruction; wherein the types of instruction actions corresponding to the first instruction and the second instruction are different.

[0006] To solve the above-mentioned technical problems, the second technical solution adopted in this application is: a conference layout device, including: a memory and a processor; the memory is used to store program instructions, and the processor is used to execute the program instructions to implement the above method.

[0007] The beneficial effects of this application are as follows: Unlike the prior art, in the technical solution of this application, after entering the custom layout interface, the corresponding display cell in the custom layout interface can be deleted in response to the first instruction, and the display window of the corresponding display cell in the custom layout interface can be deleted in response to the second instruction. The instruction actions used to trigger the generation of the first instruction and the second instruction are instruction actions of different types. This avoids the need for the user to delete two things in the meeting layout based on the same type of instruction action, and thus avoids the user from accidentally deleting the cell where the display window is located when trying to delete the display window, thereby improving the reliability of the meeting layout method. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying 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.

[0009] Figure 1 This is a flowchart illustrating the first embodiment of the meeting layout method of this application;

[0010] Figure 2 This is one of the flowcharts of the second embodiment of the meeting layout method of this application;

[0011] Figure 3 This is the second flowchart of the second embodiment of the meeting layout method of this application;

[0012] Figure 4 This is one of the schematic diagrams of an embodiment of the custom layout interface of this application;

[0013] Figure 5 This is a second schematic diagram of an embodiment of the custom layout interface of this application;

[0014] Figure 6 This is a flowchart illustrating the third embodiment of the meeting layout method of this application;

[0015] Figure 7 This is a schematic diagram of one embodiment of the layout interface of this application;

[0016] Figure 8 This is a schematic diagram of the structure of one embodiment of the meeting layout device of this application;

[0017] Figure 9 This is a schematic diagram of an embodiment of the computer-readable storage medium of this application. Detailed Implementation

[0018] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0019] The terms "first" and "second" in this application are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise expressly specified. 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 includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus.

[0020] This application first proposes a meeting layout method. In the first embodiment, such as... Figure 1 As shown, Figure 1 This is a flowchart illustrating a first embodiment of the meeting layout method of this application, which includes:

[0021] Step S11: Enter the custom layout interface.

[0022] Among them, a custom layout interface can be created and entered according to the interface creation instructions sent by the user. The specifications of the custom layout interface can be determined by the interface creation instructions.

[0023] Specifically, taking the application of this meeting layout method to a computer as an example, the custom layout interface can be a whiteboard displayed by the computer, which is used to arrange the distribution grids of meeting participants and their display windows on the whiteboard based on subsequent instructions from the user.

[0024] The aforementioned computer can also be replaced by any of the following: mobile phone, tablet, or other electronic devices with processing capabilities, depending on the actual needs. No specific restrictions are imposed here.

[0025] After entering the custom layout interface of the meeting layout based on step S11, different actions can be executed according to different received instructions. If the first instruction is received, step S12 can be executed in response to the first instruction. If the second instruction is received, step S13 can be executed in response to the second instruction, wherein the types of instruction actions corresponding to the first instruction and the second instruction are different.

[0026] Step S12: Delete the corresponding display grid in the custom layout interface.

[0027] The display grids in the custom layout interface can be user-defined grids used to place display windows to show relevant content about the participants. Specifically, the maximum number of display grids can be determined based on the size of the custom layout interface, and the number of display grids that can exist simultaneously in the custom layout interface cannot exceed this maximum number of display grids.

[0028] After the user executes the action corresponding to the first instruction, the first instruction can be generated. In response to the first instruction, the display cell specified by the first instruction in the custom layout interface can be deleted.

[0029] Specifically, taking the application of this meeting layout method to a computer as an example, after the user operates the mouse to make the mouse cursor on the computer complete the instruction action corresponding to the first instruction, the first instruction can be generated.

[0030] The aforementioned computer can also be replaced by any of the mobile phones, tablets, and other electronic devices with processing capabilities, and the commands can also be replaced by actions more compatible with the corresponding electronic devices, such as key-type actions, touch-swipe actions, etc., depending on the actual needs, and are not limited here.

[0031] Step S13: Delete the display window of the corresponding display cell in the custom layout interface.

[0032] The display window can be a video display window for displaying participants' videos, an information display window for displaying participants' information (such as ID information), a display window for playing relevant audio (such as participants' voice communication audio) without displaying any content, or other types of display windows. The specific type can be determined according to actual needs and is not limited here.

[0033] After the user executes the action corresponding to the second instruction, a second instruction can be generated. In response to this second instruction, the display window of the corresponding display cell in the custom layout interface can be deleted.

[0034] Because the types of commands for deleting display grids and display windows are different, when a user deletes a display window based on the second command, the display grid containing the display window will not be deleted at the same time, thus avoiding accidental deletion and improving the reliability of the meeting layout method.

[0035] Specifically, taking the application of this meeting layout method to a computer as an example, after the user operates the mouse to make the mouse cursor on the computer complete the instruction action corresponding to the second instruction, the second instruction can be generated.

[0036] The aforementioned computer can also be replaced by any of the mobile phones, tablets, and other electronic devices with processing capabilities, and the commands can also be replaced by actions more compatible with the corresponding electronic devices, such as key-type actions, touch-swipe actions, etc., depending on the actual needs, and are not limited here.

[0037] Optionally, the first instruction corresponds to the action of dragging a grid, and the second instruction corresponds to the action of clicking a button.

[0038] Specifically, the instruction actions corresponding to the first instruction and the instruction actions corresponding to the second instruction can be set to two significantly different types of actions, such as clicking a button and dragging a grid. This ensures that when a user clicks a button, a display grid will never be deleted, and when a user drags a grid, the display window in a display grid will never be deleted. This avoids accidental deletion and improves the reliability of the meeting layout method.

[0039] Unlike existing technologies, in the technical solution of this application, after entering the custom layout interface, the corresponding display cell in the custom layout interface can be deleted in response to a first instruction, and the display window of the corresponding display cell in the custom layout interface can be deleted in response to a second instruction. The instruction actions used to trigger the generation of the first and second instructions are instruction actions of different types. This avoids the need for the user to delete two things in the meeting layout based on the same type of instruction action, and thus avoids the user accidentally deleting the cell where the display window is located when trying to delete the display window, thereby improving the reliability of the meeting layout method.

[0040] This application also proposes a meeting layout method. In a second embodiment, the instruction action corresponding to the first instruction is a dragging action of a grid, and the instruction action corresponding to the second instruction is a clicking action of a button. Figure 2 As shown, Figure 2 This is a flowchart illustrating one of the second embodiments of the meeting layout method of this application, which includes:

[0041] Step S21: Enter the custom layout interface.

[0042] After entering the custom layout interface of the meeting layout based on step S21, different actions can be executed according to different received instructions. If a first instruction is received, step S22 can be executed in response to the first instruction. If a second instruction is received, step S23 can be executed in response to the second instruction, wherein the types of instruction actions corresponding to the first instruction and the second instruction are different.

[0043] Step S22: Delete the corresponding display grid in the custom layout interface.

[0044] Step S23: Delete the display window of the corresponding display cell in the custom layout interface.

[0045] Steps S21 to S23 correspond to steps S11 to S13 in the first embodiment, and will not be described again here.

[0046] Optionally, such as Figure 3 As shown, Figure 3 This is a second flowchart illustrating the second embodiment of the meeting layout method of this application. Step S22 may specifically include:

[0047] Step S221: In response to the first instruction, delete the display grid in the custom layout interface that was dragged to the first preset area based on the instruction action corresponding to the first instruction.

[0048] Specifically, users can generate a first instruction by executing the instruction action corresponding to the first instruction, and then determine and delete the display cells that need to be deleted in the custom layout interface based on the first instruction.

[0049] Taking the application of this meeting layout method to computers as an example, such as Figure 4 As shown, Figure 4 This is one of the schematic diagrams of an embodiment of the custom layout interface of this application. The user can manipulate the mouse to make the computer cursor select the display cell that needs to be deleted in the custom layout interface. The selected display cell will move with the movement of the computer cursor. The user can drag the display cell that needs to be deleted to the first preset area (such as the module icon corresponding to the grid bar or trash can) and no longer select the display cell, so that the display cell can be deleted.

[0050] In addition to the above methods, other types of command actions can be configured for the first command to be triggered by the user, which is not limited here.

[0051] Based on the above method, the display cell that needs to be deleted in the custom layout interface can be dragged to the specified location to complete the deletion of the specified display cell, avoiding accidental deletion and improving the reliability of the meeting layout method.

[0052] Optionally, such as Figure 3 As shown, step S23 may specifically include:

[0053] Step S231: In response to the second instruction, delete the display window of the window whose delete button was clicked in the custom layout interface based on the instruction action corresponding to the second instruction.

[0054] Specifically, users can generate a second instruction by executing the corresponding instruction action, and then determine and delete the display window that needs to be deleted in the corresponding display cell of the custom layout interface according to the second instruction.

[0055] Taking the application of this meeting layout method to computers as an example, such as Figure 5 As shown, Figure 5 This is a second schematic diagram of an embodiment of the custom layout interface of this application. The display window can be configured with a delete button. The user can manipulate the mouse so that the computer cursor clicks the delete button of the display window to be deleted, and the display window can be deleted.

[0056] In addition to the above methods, other types of command actions can be configured for the second command to be triggered by the user, which is not limited here.

[0057] Based on the above method, the specified display window can be deleted by clicking on the display window to be deleted in the custom layout interface, thus avoiding accidental deletion and improving the reliability of the meeting layout method.

[0058] Optionally, after step S21, the meeting layout method may further include:

[0059] In response to the third instruction, it is created in the custom layout interface and dragged from the second preset area to the display grid in the custom layout interface based on the instruction action corresponding to the third instruction.

[0060] The third instruction corresponds to the action of dragging a grid, and the second preset area has at least two sizes of display grids.

[0061] Specifically, such as Figure 4 As shown, the second preset area can be the same as the first preset area mentioned above, for example, both can be grids. The grid can be set with at least two sizes of display grids or their corresponding icons. Users can drag a display grid of a certain size or its icon from the grid to the custom layout interface to complete the creation of the corresponding display grid.

[0062] In practice, the grid can contain multiple cells with the same aspect ratio. For example, the grid might have five cells with the same aspect ratio: the first cell is the smallest, the second cell has a side length twice that of the first, the third cell has a side length three times that of the first, the fourth cell has a side length four times that of the first, and the fifth cell has a side length five times that of the first. Users can create cells of the desired size by dragging and dropping cells as described above. Furthermore, cells created in the custom layout interface can be moved in units of the side length of the first cell, allowing users to adjust the position of each cell in the titrator layout interface according to their needs.

[0063] Optionally, after step S21, the meeting layout method further includes:

[0064] In response to the fourth instruction, a display window is set in the display cell corresponding to the fourth instruction in the custom layout interface.

[0065] Specifically, each display cell can be equipped with a video source setting button. Users can click this button to select a participant's video source from the pop-up participant list to be displayed in the display window; alternatively, they can drag a participant's icon from the participant list to the corresponding display cell to create a display window for that cell; other methods can also be used to set display windows in the display cells, which are not limited here. Furthermore, the display window can be the same size as the display cell or smaller, which is not limited here. The video source setting button can also be replaced with an information setting button or an image setting button, allowing users to select whether to display the participant's relevant information.

[0066] Unlike existing technologies, in the technical solution of this application, after entering the custom layout interface, the corresponding display cell in the custom layout interface can be deleted in response to a first instruction, and the display window of the corresponding display cell in the custom layout interface can be deleted in response to a second instruction. The instruction actions used to trigger the generation of the first and second instructions are instruction actions of different types. This avoids the need for the user to delete two things in the meeting layout based on the same type of instruction action, and thus avoids the user accidentally deleting the cell where the display window is located when trying to delete the display window, thereby improving the reliability of the meeting layout method.

[0067] This application also proposes a meeting layout method. In the third embodiment, the meeting layout method includes the same steps as steps S11 to S13 in the first embodiment, which will not be repeated here.

[0068] like Figure 6 As shown, Figure 6 This is a flowchart illustrating a third embodiment of the meeting layout method of this application. The meeting layout method further includes:

[0069] Step S31: Based on the current state of the custom layout interface, generate and upload the custom layout data to the server.

[0070] After the user sets the position of each display cell and its display window in the custom layout interface using the various commands or other commands mentioned above, the current state of the custom layout interface can be saved as custom layout data. This custom layout data is used to record the layout information of the custom layout interface in the current state.

[0071] The custom layout data can then be uploaded to the server. The meeting layout can be generated using any type of electronic device, depending on the specific requirements. No restrictions are imposed here.

[0072] Step S32: The client obtains custom layout data from the server and sets the meeting layout based on the custom layout data.

[0073] The client can download the custom layout data from the server and lay out the interface on the meeting software according to the layout information contained in the custom layout data.

[0074] Specifically, the custom layout data may include the position data corresponding to each display cell, whether a display window is set on each display cell, and which participant the display window corresponds to by default. The specifics can be determined according to actual needs and are not limited here.

[0075] Optionally, step S32 may specifically include:

[0076] The client determines the aspect ratio of the meeting layout resolution based on the custom layout data, which is denoted as the first aspect ratio.

[0077] The client obtains the aspect ratio of the client's display resolution, which is denoted as the second aspect ratio.

[0078] The client sets the meeting layout based on the first aspect ratio, the second aspect ratio, and custom layout data.

[0079] Specifically, after obtaining the custom layout data, the client can determine the aspect ratio of the meeting layout resolution corresponding to the custom layout data, which is the aspect ratio of the entire interface when the meeting is conducted without distortion based on the custom layout data, denoted as the first aspect ratio.

[0080] The client can also obtain the aspect ratio of the resolution of the display device that the client is connected to or that is set on the client, denoted as the second aspect ratio.

[0081] Based on a first aspect ratio and a second aspect ratio, the layout interface generated from custom layout data can be displayed to its maximum potential without distortion on the client's corresponding display device. This approach effectively improves the experience for attendees.

[0082] Furthermore, the client sets the meeting layout based on the first aspect ratio, the second aspect ratio, and custom layout data, which may include:

[0083] In response to the first aspect ratio being greater than the second aspect ratio, the client obtains the actual display width of the client and, based on the custom layout data, sets the meeting layout with the actual display width of the client as the display width of the layout interface and the first aspect ratio as the display ratio of the layout interface.

[0084] The actual display width on the client side is the maximum display width of the display device corresponding to the client. When the first aspect ratio is greater than the second aspect ratio, the display width of the layout interface must be less than or equal to the actual display width on the client side. Otherwise, the display device corresponding to the client side will not be able to display the entire layout interface completely, or the client will be able to display the entire layout interface completely, but the layout interface will be compressed and distorted.

[0085] In response to the condition that the first aspect ratio is not greater than the second aspect ratio, the client obtains the actual display height of the client and sets the meeting layout based on the custom layout data, using the actual display height of the client as the display height of the layout interface and the first aspect ratio as the display ratio of the layout interface.

[0086] The actual display height on the client side is the maximum display height of the corresponding display device. When the first aspect ratio is not greater than the second aspect ratio, the display height of the layout interface must be less than or equal to the actual display height on the client side. Otherwise, the corresponding display device on the client side will not be able to display the entire layout interface completely, or the client will be able to display the entire layout interface completely, but the layout interface will be compressed and distorted.

[0087] Based on the above method, the layout interface corresponding to the custom layout data can be displayed completely and without distortion on any display device corresponding to the client, thus improving the experience of the participants.

[0088] In an application scenario, such as Figure 7 As shown in (A), the layout interface corresponding to the custom layout data includes display grids 1-4. Display grids 1-4 are four rectangles with the same aspect ratio. The side length of display grid 1 and the side length of display grid 2 are three times and two times the side length of display grid 3, respectively. Display grids 3 and 4 have the same side length. Therefore, taking display grid 3 as the unit grid, the position data corresponding to the display grid can be determined as follows:

[0089] Display cell 1: 0 units from the top edge and 0 units from the left edge.

[0090] Display grid 2: 0 units from the top edge and 3 units from the left edge.

[0091] Display grid 3: 2 units from the top edge and 3 units from the left edge.

[0092] Display grid 4: 2 units from the top edge and 4 units from the left edge.

[0093] For example, in custom layout data, the code corresponding to the above position data can be as follows:

[0094]

[0095] Among them, width represents the width, height represents the height, top represents the distance from the top edge, left represents the distance from the left edge, and cell represents the display grid.

[0096] [[ID=],[3]]After obtaining the custom layout data, assuming that the aspect ratio of the confirmed conference layout resolution is 16:9, then we can get:

[0097] viewWidth:viewHeight = width * 16:height * 9

[0098] Among them, viewWidth is the width to be displayed on the display device corresponding to the layout interface on the client, viewHeight is the height to be displayed on the display device corresponding to the layout interface on the client, width is the height of the unit cell, and height is the width of the unit cell.

[0099] If we want to display the layout interface on this display device as large as possible without deformation, then:

[0100] When windowsWidth:windowsHeight >= viewWidth:viewHeight, that is, when the first aspect ratio is not greater than the second aspect ratio, it is necessary to make:

[0101] viewWidth = windowsHeight * width * 16 / (height * 9)

[0102] viewHeight = windowsHeight

[0103] Among them, windowsWidth is the maximum display width of the display device, windowsHeight is the maximum display height of the display device, viewWidth is the display width of the layout interface, and viewHeight is the display height of the layout interface.

[0104] When windowsWidth:windowsHeight < viewWidth:viewHeight, that is, when the first aspect ratio is greater than the second aspect ratio, it is necessary to make:

[0105] viewWidth = windowsWidth;

[0106] viewHeight = windowsWidth * (height * 9) / (width * 16)

[0107] In addition, it is also necessary to make the layout interface centered in the display device:

[0108] viewTop=(windowsHeight-viewHeight) / 2

[0109] viewLeft=(windowsWidth-viewWidth) / 2

[0110] Where viewTop is the distance from the top edge of the layout, and viewLeft is the distance from the left edge.

[0111] Finally, the actual size and position of each display cell need to be calculated:

[0112] perCellWidth=viewWidth / width

[0113] perCellHeight=viewHeight / height

[0114] cell.trueWidth=cell.width*perCellWidth

[0115] cell.trueHeight=cell.height*perCellHeight

[0116] cell.trueLeft=cell.left*perCellWidth

[0117] cell.trueTop=cell.top*perCellHeight

[0118] Where cell.trueWidth is the actual width of the displayed cell, cell.trueHeight is the actual height of the displayed cell, cell.trueLeft is the actual distance of the displayed cell from the left edge, and cell.trueTop is the actual distance of the displayed cell from the top edge.

[0119] By displaying the actual data of the aforementioned display grid on the display device, the layout interface can be displayed on the display device in a maximized and undistorted manner, such as... Figure 7 (B) shows the layout interface displayed on the client's display device based on the above method when the first aspect ratio is not greater than the second aspect ratio. Figure 7 (C) shows the layout interface displayed on the client's display device based on the above method when the first aspect ratio is greater than the second aspect ratio. The black border represents the part of the display screen on the display device that has no content displayed.

[0120] Unlike existing technologies, in the technical solution of this application, after entering the custom layout interface, the corresponding display cell in the custom layout interface can be deleted in response to a first instruction, and the display window of the corresponding display cell in the custom layout interface can be deleted in response to a second instruction. The instruction actions used to trigger the generation of the first and second instructions are instruction actions of different types. This avoids the need for the user to delete two things in the meeting layout based on the same type of instruction action, and thus avoids the user accidentally deleting the cell where the display window is located when trying to delete the display window, thereby improving the reliability of the meeting layout method.

[0121] This application also proposes a meeting layout device, such as Figure 8 As shown, Figure 8 This is a schematic diagram of the structure of an embodiment of the conference layout device of this application. The conference layout device 80 includes: a processor 81, a memory 82, and a bus 83.

[0122] The processor 81 and the memory 82 are connected to the bus 83. The memory 82 stores program instructions, and the processor 81 is used to execute the program instructions to implement the meeting layout method in the above embodiment.

[0123] In this embodiment, processor 81 can also be referred to as CPU (Central Processing Unit). Processor 81 may be an integrated circuit chip with signal processing capabilities. Processor 81 can also be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor, or processor 81 can be any conventional processor.

[0124] Unlike existing technologies, in the technical solution of this application, after entering the custom layout interface, the corresponding display cell in the custom layout interface can be deleted in response to a first instruction, and the display window of the corresponding display cell in the custom layout interface can be deleted in response to a second instruction. The instruction actions used to trigger the generation of the first and second instructions are instruction actions of different types. This avoids the need for the user to delete two things in the meeting layout based on the same type of instruction action, and thus avoids the user accidentally deleting the cell where the display window is located when trying to delete the display window, thereby improving the reliability of the meeting layout method.

[0125] This application also proposes a computer-readable storage medium, such as Figure 9 As shown, Figure 9This is a schematic diagram of the structure of an embodiment of the computer-readable storage medium of this application. The computer-readable storage medium 90 stores program instructions 91 thereon. When the program instructions 91 are executed by a processor (not shown), they implement the meeting layout method in the above embodiment.

[0126] In this embodiment, the computer-readable storage medium 90 may be, but is not limited to, a USB flash drive, SD card, PD optical drive, portable hard drive, high-capacity floppy drive, flash memory, multimedia memory card, storage unit in a server, FPGA, or ASIC, etc.

[0127] Unlike existing technologies, in the technical solution of this application, after entering the custom layout interface, the corresponding display cell in the custom layout interface can be deleted in response to a first instruction, and the display window of the corresponding display cell in the custom layout interface can be deleted in response to a second instruction. The instruction actions used to trigger the generation of the first and second instructions are instruction actions of different types. This avoids the need for the user to delete two things in the meeting layout based on the same type of instruction action, and thus avoids the user accidentally deleting the cell where the display window is located when trying to delete the display window, thereby improving the reliability of the meeting layout method.

[0128] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A meeting layout method, characterized in that, include: Enter the custom layout interface; In response to the first instruction, delete the corresponding display cell in the custom layout interface; In response to the second instruction, delete the display window of the corresponding display cell in the custom layout interface; The first instruction and the second instruction correspond to different types of instruction actions.

2. The meeting layout method according to claim 1, characterized in that, The first instruction corresponds to the action of dragging a grid, and the second instruction corresponds to the action of clicking a button.

3. The meeting layout method according to claim 2, characterized in that, The step of deleting the corresponding display cell in the custom layout interface in response to the first instruction includes: In response to the first instruction, the display grid that was dragged to the first preset area in the custom layout interface based on the instruction action corresponding to the first instruction is deleted.

4. The meeting layout method according to claim 2, characterized in that, The step of deleting the display window of the corresponding display cell in the custom layout interface in response to the second instruction includes: In response to the second instruction, delete the display window of the window whose delete button was clicked in the custom layout interface based on the instruction action corresponding to the second instruction.

5. The meeting layout method according to any one of claims 1 to 4, characterized in that, The meeting layout method also includes: Based on the current state of the custom layout interface, generate and upload custom layout data to the server. The client obtains the custom layout data from the server and sets the meeting layout based on the custom layout data.

6. The meeting layout method according to claim 5, characterized in that, The client obtains the custom layout data from the server and sets the meeting layout based on the custom layout data, including: Based on the custom layout data, the client determines the aspect ratio of the meeting layout resolution, which is denoted as the first aspect ratio; The client obtains the aspect ratio of the client's display resolution, which is denoted as the second aspect ratio; The client sets the meeting layout based on the first aspect ratio, the second aspect ratio, and the custom layout data.

7. The meeting layout method according to claim 6, characterized in that, The client configures the meeting layout based on the first aspect ratio, the second aspect ratio, and the custom layout data, including: In response to the first aspect ratio being greater than the second aspect ratio, the client obtains the actual display width of the client and, based on the custom layout data, sets the meeting layout with the actual display width of the client as the display width of the layout interface and the first aspect ratio as the display ratio of the layout interface. In response to the first aspect ratio not being greater than the second aspect ratio, the client obtains the client's actual display height and, based on the custom layout data, sets the meeting layout with the client's actual display height as the layout interface display height and the first aspect ratio as the layout interface display ratio.

8. The meeting layout method according to any one of claims 1 to 4, characterized in that, The third instruction corresponds to the action of dragging a grid. The meeting layout method also includes: In response to the third instruction, it is created in the custom layout interface and dragged from the second preset area to the display grid in the custom layout interface based on the instruction action corresponding to the third instruction. The second preset area contains at least two sizes of display grids.

9. The meeting layout method according to any one of claims 1 to 4, characterized in that, The meeting layout method also includes: In response to the fourth instruction, a display window is set in the display grid corresponding to the fourth instruction in the custom layout interface.

10. A conference layout device, characterized in that, include: Memory and processor; The memory is used to store program instructions, and the processor is used to execute the program instructions to implement the method as described in any one of claims 1 to 9.

Images