Separate event modeling and management systems

By automatically detecting and adjusting node overlap, the self-adjustment of the node editor workspace in three-dimensional modeling is achieved, which solves the chaotic problem caused by node aggregation and improves user operation experience and layout management efficiency.

CN115516476BActive Publication Date: 2024-12-03MAXON COMPUTER GMBH 61352
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202180031319.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-02-27
Filing Date
2021-02-25
Publication Date
2024-12-03
Estimated Expiration
2041-02-25

AI Technical Summary

Technical Problem

During the three-dimensional modeling process, the workspace of the node editor is easily confused due to node aggregation, making it difficult for users to visualize and place new nodes. Existing solutions such as node groups or collapses require manual operation by users and may destroy the original There is a layout that causes workflow interruption.

Method used

By detecting the overlap of new nodes and existing nodes, automatically repositioning and scaling nodes, ensuring that nodes are evenly distributed until overlap is eliminated, and maintaining the consistent node size before scaling, allowing users to adjust the workspace for easier viewing of layouts.

Benefits of technology

It realizes an automated solution that does not destroy the original layout of users, reduces user operation burden, improves the node capacity and visualization of the workspace, and simplifies node layout management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115516476B_ABST
    Figure CN115516476B_ABST
Patent Text Reader

Abstract

A system and method for automatically adjusting a workspace including a plurality of nodes for a continuous workflow is disclosed. A method includes receiving a new node in a workspace and determining that the new node overlaps with one or more nodes. Based on the determination, a group of nodes within a predetermined distance of the overlap can be repositioned, the group of nodes including the new node and the one or more nodes. After determining that the new node still overlaps with the one or more nodes, the group of nodes can be reduced until there is no overlap.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 16 / 802,734, filed on February 27, 2020, which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure relates to systems and methods for three-dimensional modeling process enhancement. More particularly, the present disclosure relates to systems and methods for adjusting the placement and scaling of nodes in a workspace of a node editor. Background Art

[0004] In three-dimensional (3D) modeling, a node editor allows users to create objects by routing basic properties through a set of nodes. Each node can perform operations on the properties, thereby changing how the object will appear visually in 3D space, and can pass the modified properties to the next node. By utilizing various nodes and making appropriate connections between them, the desired object appearance can be achieved.

[0005] The background description provided herein is for the purpose of generally presenting the context of the present disclosure. Unless otherwise indicated herein, the materials described in this section are not prior art and are not admitted to be prior art or suggestions of prior art by inclusion in this section. Summary of the invention

[0006] One embodiment provides a computer-implemented method for automatically adjusting a workspace including multiple nodes for a continuous workflow, the method comprising: receiving a new node in the workspace; determining that the new node overlaps with one or more nodes; repositioning a group of nodes within a predetermined distance of the overlap, the group of nodes including the new node and the one or more nodes; determining that the new node still overlaps with the one or more nodes; and shrinking the group of nodes until there is no overlap.

[0007] One embodiment provides a system, including: one or more processors; and one or more computer-readable media including instructions, which, when executed by the one or more processors, cause the one or more processors to perform operations for automatically adjusting a workspace including a plurality of nodes for a continuous workflow. The operations may include: receiving a new node in the workspace; determining that the new node overlaps with one or more nodes; repositioning a set of nodes within a predetermined distance of the overlap, the set of nodes including the new node and the one or more nodes; determining that the new node still overlaps with the one or more nodes; and shrinking the set of nodes until there is no overlap.

[0008] One embodiment provides one or more non-transitory computer-readable media including instructions that, when executed by one or more processors, cause the one or more processors to perform operations for automatically adjusting a workspace including a plurality of nodes for a persistent workflow. The operations may include: receiving a new node in the workspace; determining that the new node overlaps with one or more nodes; repositioning a set of nodes within a predetermined distance of the overlap, the set of nodes including the new node and the one or more nodes; determining that the new node still overlaps with the one or more nodes; and shrinking the set of nodes until there is no overlap.

[0009] Additional purposes and advantages of the disclosed embodiments will be set forth in part in the following description, and in part will be clear from the description, or may be understood through the practice of the disclosed embodiments. The purposes and advantages of the disclosed embodiments will be realized and obtained by means of the elements and combinations particularly pointed out in the appended claims.

[0010] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosed embodiments, as claimed. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various exemplary embodiments and, together with the description, serve to explain the principles of the disclosed embodiments.

[0012] Figure 1 An exemplary workspace of a node editor of a modeling application is shown.

[0013] Figure 2A-2E Illustrated are sequential views of an exemplary self-adjusting workspace according to one aspect of the present disclosure.

[0014] Figure 3 is a flow chart illustrating an exemplary method of adjusting a workspace of a node editor according to one aspect of the present disclosure.

[0015] Figures 4A-4C Illustrated are sequential views of an exemplary self-adjusting workspace during node repositioning according to one aspect of the present disclosure.

[0016] Figures 5A-5C Illustrated are sequential views of an exemplary self-adjusting workspace in which overlap between nodes is preserved after repositioning.

[0017] Fig. 6A An exemplary self-adjusting workspace is shown as the view of the workspace is panned outward to show all nodes according to one aspect of the present disclosure.

[0018] Figure 6B According to one aspect of the present disclosure Fig. 6A An adjusted view of an exemplary self-adjusting workspace of .

[0019] Fig. 7A An exemplary self-adjusting workspace including a plurality of nodes according to one aspect of the present disclosure is shown.

[0020] Figure 7B Shows the corresponding Fig. 7A Node density plot of the self-adjusting workspace. DETAILED DESCRIPTION

[0021] The following embodiments describe systems and methods for 3D modeling process enhancement, and more particularly for adjusting the placement and scaling of nodes in a node editor's workspace.

[0022] 3D modeling software allows users to navigate and inspect objects created in a virtual 3D space, and handle small details as well as large scene elements without losing context. The node editor of such 3D modeling software can enable customization of the appearance of an object using nodes and node connections, thereby allowing users to manipulate object properties to desired specifications. Generally speaking, the workspace of a node editor can be composed of i) nodes representing calculations and ii) connections between nodes to control how data flows through the nodes. When creating complex objects or scenes, the workspace of a node editor may quickly become crowded with nodes, making visualization and / or adding nodes more difficult and cumbersome. For example, a user may have to manually move, group, and / or rescale existing nodes to make room for additional nodes in the workspace.

[0023] One solution to this problem is to arrange existing nodes into node groups, or to collapse nodes. Both of these options have the disadvantage of requiring additional actions from the user to access the nodes again. Furthermore, the node groups or collapsed areas may not necessarily be created in a logical and / or functional manner, making the resulting layout difficult to interpret. Another solution is automatic layout. This method technique also has the disadvantage of destroying the original setup or layout developed by the user, which can cause significant disruption or confusion in the workflow.

[0024] The technology envisioned in the present disclosure can alleviate or minimize the above-mentioned problems. In general, the technology discussed in the present disclosure provides an automated solution that does not destroy the user's original node layout by repositioning and / or rescaling nodes based on the current scale and / or size of each node in the workspace and / or the distance from each other. In one embodiment, in response to receiving a new node in the workspace, any overlap with an existing node can be detected. If there is an overlap, a group of nodes of overlapping neighbors can be repositioned to even out the node distribution around the new node. If there is still an overlap after the repositioning, the group of nodes can be reduced until there is no overlap. Alternatively, the group of nodes can be scaled without an initial repositioning, or the scaling can occur before any repositioning. Additionally, the view of the workspace can be adjusted to visually maintain their size (i.e., the node size before scaling) before the nodes are reduced. By repositioning and / or rescaling nodes, the workspace can be able to accommodate as many nodes as possible in a small area that the user feels comfortable with. Users can be allowed to zoom in and out of the area of ​​interest within the workspace to better view and / or understand the node layout.

[0025] The subject matter of the present disclosure will now be described more fully below with reference to the accompanying drawings, which form a part of the present disclosure and show specific exemplary embodiments by way of illustration. An embodiment or implementation described herein as "exemplary" should not be interpreted as being preferred or advantageous, for example, relative to other embodiments or implementations; rather, it is intended to reflect or indicate that (one or more) embodiments are (one or more) "example" embodiments. The subject matter can be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be interpreted as not being limited to any exemplary embodiment set forth herein; the exemplary embodiments are provided for illustrative purposes only. Likewise, a reasonably broad scope of the subject matter to be claimed or covered is intended. For example, among other things, the subject matter can be embodied as a method, device, component, or system. Therefore, the embodiment can take the form of hardware, software, firmware, or any combination thereof, for example. Therefore, the following detailed description is not intended to be considered in a restrictive sense.

[0026] It should also be noted that all numerical values ​​disclosed herein may vary from the disclosed numerical values ​​by ±10% (unless a different variation is specified). In addition, all relative terms such as "approximately", "substantially", "approximately", etc. are used to indicate a possible variation of ±10% (unless otherwise indicated or another variation is specified).

[0027] Throughout the specification and claims, in addition to the meanings explicitly stated, terms may have slightly different meanings that are implied or suggested by the context. Likewise, the phrases "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and the phrase "in another embodiment" as used herein does not necessarily refer to a different embodiment. For example, it is intended that the claimed subject matter includes the exemplary embodiments in whole or in part.

[0028] The terminology used below may be interpreted in its broadest reasonable manner, even though it is used in conjunction with the detailed description of certain specific examples of the present disclosure. In fact, certain terms may even be emphasized below; however, any term intended to be interpreted in any restrictive manner will be openly and specifically defined in the detailed description section as such.

[0029] Now referring to the accompanying drawings, Figure 1 An exemplary workspace 100 of a node editor for a modeling application (e.g., a 3D modeling application) is shown. Using the node editor, a user can configure various visual attributes of an object by creating appropriate nodes (e.g., node 110) and connections (e.g., connection 115) between the inputs and outputs of those nodes. As more visual attributes are configured and added, the workspace 100 may become crowded with nodes and connections, making it difficult for the user to interpret the layout and / or place additional nodes in the limited space of the workspace 100. In addition, the user may have to resize existing nodes to make room for any future nodes as well as the size of the nodes being added. The user may also need to place nodes in undesirable locations just to accommodate all the required nodes in the limited space, which makes interpreting and placing additional nodes even more cumbersome.

[0030] Figure 2A-2E 1 illustrates a sequential view of an exemplary self-adjusting workspace 200 according to one aspect of the present disclosure. The self-adjusting workspace 200 can be configured to mitigate the problems discussed above. For simplicity and ease of understanding, Figure 2A-2E The nodes depicted in the workspace 200 are illustrated only as rectangles of different sizes, and connections between the nodes are not shown. However, one of ordinary skill in the art will recognize that the nodes can be of various types associated with corresponding operations, and can each include (one or more) inputs and / or (one or more) outputs that enable connections to and / or from other nodes in the workspace 200.

[0031] Figure 2A A plurality of nodes are shown present in workspace 200, including nodes 20, 21, 22, 23, 24, 25, and 26. The sizes of the nodes may be different or the same. Figure 2AThe nodes in may represent a layout that has not been changed from a user-configured layout, or may represent a layout that has been automatically changed using the techniques of the present disclosure. Figure 2A The workspace 200 in FIG. 2 looks cluttered, making it difficult and cumbersome for the user to place additional nodes at desired locations.

[0032] To more clearly explain the purpose of the operation of the self-adjusting workspace 200, Figure 2B-2D A partial view of a self-adjusting workspace 200 is depicted. Figure 2B Depicted is the process of adding a new node to the workspace 200. Figure 2A A partial view of a self-adjusting workspace 200. The space between nodes 20, 21, 22, 23, 24, 25, and 26 appears to be finite, which may cause overlap when a new node is added near any of these existing nodes. Figure 2C-2D The operation of the self-adjusting workspace 200 is depicted when such a new node is added to the workspace 200. Figure 2C-2D In response to the user placing a new node 27 at a cluttered area of ​​the workspace 200, some existing nodes may be moved from their previous locations to make room for the new node 27. For example, nodes 20, 21, 22, 23, 24, 25, and 26 may be relocated, such as from Figure 2B to Figure 2C and from Figure 2C to Figure 2D 's node position change. More specifically, nodes 20, 21, 22, 23, 24, 25 and / or 26 can be moved away or pushed away from the new node 27 to make room for the new node 27 and prevent the new node 27 and existing nodes from overlapping each other. In some embodiments, node movement can be weighted so that closely grouped nodes maintain their distance from each other, and farther nodes are moved even farther to provide space for closely grouped nodes to be relocated. When weighting the degree of movement of the nodes, existing node connections (e.g., the number of connections between the new node and the existing nodes) can also be considered. From the user's perspective, the nodes may appear to be pushed away from each other, and pushed away from where overlap may have occurred, and even more so when the overlapping neighbors are more densely populated with nodes (i.e., when the node density is large). In addition to repositioning, or alternatively, if overlap still exists even after repositioning the nodes, all or a subset of the new node 27 and the existing nodes 20, 21, 22, 23, 24, 25 and 26 can be rescaled (e.g., reduced). In one embodiment, the rescaling can be based on the current scale and / or size of each node within a predetermined distance from the overlap. In some embodiments, the rescaling can be performed using node density (i.e., node weight) information associated with the new node 27 and the area around the existing nodes (e.g., the area within a predetermined distance from the overlap).

[0033] Figure 2E Depicted is the self-adjusting workspace 200 after the nodes have been rescaled. In addition to nodes 20, 21, 22, 23, 24, 25, 26 and 27 as described above with reference Figure 2B-2D In addition to being repositioned as explained, the nodes can also be rescaled (e.g., reduced) to eliminate additional overlaps between nodes. If overlaps still exist after repositioning, all or subsets of the new node 27 and existing nodes 20, 21, 22, 23, 24, 25, and 26 can be rescaled (e.g., reduced). In one embodiment, rescaling can be based on the current scale and / or size of each node within a predetermined distance from the overlap. In an alternative or additional embodiment, node density (i.e., node weight) information associated with the area around the new node 27 and the existing node (e.g., the area within a predetermined distance from the overlap) can be used to perform rescaling. For example, the node can be rescaled by evaluating the node density associated with the new node 27 or the overlapping neighbor (i.e., the local area within a predetermined distance). In one embodiment, the repositioning and / or rescaling of the nodes can be performed so that the distance between the nodes remains the same. In another embodiment, the distance between the nodes after repositioning and / or rescaling can be substantially proportional to the distance between the nodes before repositioning and / or rescaling. The repositioning and rescaling of the nodes will be explained in more detail below.

[0034] Figure 3 3 is a flowchart illustrating an exemplary method of adjusting a workspace of a node editor according to one aspect of the present disclosure. It is noteworthy that method 300 can be performed by a modeling application including a node editor to maintain a consistent, interpretable node layout in a workspace. At step 310, the modeling application can receive a new node in a workspace including one or more nodes (i.e., one or more existing nodes). For example, a new node can be added to the workspace when a user creates a new node, drags and drops it onto the workspace, or when a user triggers a function that causes a new node to be created. At step 320, the modeling application can determine whether the new node overlaps with one or more nodes in the workspace. If it is determined that the new node does not overlap with any node in the workspace, method 300 can proceed to step 370, where the workspace adjustment process terminates. On the other hand, if it is determined that the new node overlaps with one or more nodes in the workspace, method 300 can proceed to step 330.

[0035] At step 330, the modeling application may reposition a set of nodes within the (one or more) overlapping neighbors so as to eliminate the (one or more) overlaps. The set of nodes may include the new node and one or more nodes overlapping the new node. The set of nodes may further include one or more other nodes in the workspace, including nodes that do not overlap the new node. In general, the overlapping neighbors may cover an area that is in close proximity to the detected (one or more) overlaps, for example, such as an area within a predetermined distance from the detected (one or more) overlaps. In one embodiment, the overlapping neighbors may include a circular area extending from the center point of the (one or more) overlaps. The radius of the circular area may be approximately twice the size of the new node, or approximately twice the size of the node overlapping the new node. The size of the new or existing node may be the side length of the node, which is typically rectangular. However, the radius of the circular area may be configured to any specification by the developer or administrator of the modeling application using the size of the nodes and / or any (one or more) overlaps in the workspace. For example, the radius of the circular area may be approximately three times the size of the new node, or approximately three times the size of the node overlapping the new node. The set of nodes within overlapping neighbors can be repositioned so that the distribution of nodes associated with the overlapping neighbors is evened out (i.e., a local relaxation technique). In other words, the set of nodes can be moved away from the overlapping position(s) (i.e., "relaxed"). In some embodiments, when the set of nodes within overlapping neighbors are pushed away from the overlap, certain nodes outside of the overlapping neighbors can also be pushed away, thereby providing additional space for the set of nodes to be repositioned. In such a case, the space between clusters of tightly grouped nodes can be widened.

[0036] In an alternative or additional embodiment, the repositioning can be based on the number of connection hops between the new node and each of the one or more nodes that overlap with the new node. The number of connection hops between two nodes can indicate the strength of the relationship between the two nodes, or the closeness between the two nodes. For example, the greater the number of intermediate nodes between the two nodes, the weaker the relationship between the two nodes. In the case of a weaker relationship, the "relaxation" of the node from the new node (i.e., the degree of movement away from the new node) can be more elastic, meaning that the node can be pushed farther away from its previous position. In the case of a stronger relationship, the "relaxation" of the node from the new node can be less elastic, meaning that the node can be moved, but can remain relatively close to its previous position. Relaxation techniques based on the number of connection hops between nodes can be beneficial in keeping closely related nodes within close proximity to each other, thereby enabling a user to discern the strength of the relationship between nodes based on the distance between the nodes and / or the degree of movement away from the new node.

[0037] Figures 4A-4C4 illustrates a sequential view of an exemplary self-adjusting workspace 400 during node relocation according to one aspect of the present disclosure. Notably, Figures 4A-4C The operations illustrated in can be performed by a modeling application including a node editor to reposition nodes in response to identifying overlapping nodes in the workspace 400 when adding new nodes. Figure 4A In the example of , workspace 400 may initially contain nodes 40, 41, 42, 43, and 44. Figure 4B In , a new node 45 may be added to the workspace 400. The user may add the new node 45 to a location where there is insufficient space for the new node 45, thereby creating an overlap with one or more of the existing nodes 40, 41, 42, 43, and 44. Figure 4B In the example of , new node 45 has been inserted at the approximate center point of surrounding nodes 41, 42, 43, and 44, and nodes 43 and 44 overlap with new node 45. The modeling application can detect such an overlap and can determine the neighbors of overlap 400 based on the location of the overlap. As explained above, the neighbors of an overlap (e.g., the neighbors of overlap 400) can include a circular area extending from the center point of the overlap, the radius of the circular area being, for example, approximately twice the size of the new node (e.g., node 45) or the overlapping node (e.g., nodes 43, 44, or 45) (e.g., horizontal edges, vertical edges, diagonal lines extending from the upper right corner to the lower left corner, etc.). However, the neighbors of an overlap can be configured to any suitable specification. Figure 4B , the neighborhood of overlap 400 completely surrounds new node 45 and existing nodes 43 and 44, which means that the entirety of new node 45 and existing nodes 43 and 44 are included within the neighborhood of overlap 400. Nodes completely surrounded by the neighborhood of overlap 400 may be part of a "set of nodes" as referred to throughout this disclosure. Figure 4B The set of nodes depicted in (e.g., nodes 43, 44, and 45) includes only overlapping nodes, but the set of nodes may include one or more other nodes that do not overlap with the new node 45, depending on how a developer or administrator of the modeling application has configured the parameters defining the neighbors of overlap 500.

[0038] Continue to refer Figure 4B , the set of nodes including the new node 45 and the existing nodes 43 and 44 may be repositioned as discussed above with reference to step 330 of method 300 . Figure 4C A repositioned set of nodes is depicted in .

[0039] Alternatively or additionally, the relocation may take into account the number of connection hops between the new node 45 and each of the nodes 43 and 45 that overlap with the new node 45. Figure 4B, the number of connection hops between new node 45 and node 43 is four, with new node 45 connected to node 43 via intermediate nodes 40, 41, and 42. The number of connection hops between new node 45 and node 44 is two, with new node 45 connected to node 44 via intermediate node 42. Based on the number of connection hops, the modeling application may determine that the connection or relationship between new node 45 and node 44 is stronger than the connection or relationship between new node 45 and node 43.

[0040] As explained above, nodes that have relatively weak connections to a new node may be moved farther from their previous locations than nodes that have relatively strong connections to the new node. Figure 4C In the example, node 43, which has a relatively weak connection with new node 45, has been moved away from its Figure 4A-4B The previous position shown in is further away, and the relatively strongly connected node 44 has moved slightly away from its previous position in Figure 4A-4B It should be noted that the new node may also be repositioned from its initial position (e.g., the position where the user drags and drops the new node onto the workspace, the position where the new node is created in response to the user activating a function within the node editor, etc.). For example, in Figure 4B-4C In the example, the new node 45 has been Figure 4B Its initial position is shown as moving to Figure 4C Position shown.

[0041] Reference again Figure 3 At step 340, the modeling application may determine whether the new node still overlaps one or more nodes in the workspace even after repositioning the set of nodes at step 330. If it is determined that the new node no longer overlaps one or more nodes, the method 300 may proceed to step 370, where the workspace adjustment process terminates. On the other hand, if it is determined that the new node still overlaps one or more nodes, the method 300 may proceed to step 350. As an example, Figures 5A-5C 5 illustrates a sequential view of an exemplary self-adjusting workspace 500 in which overlaps between multiple nodes still exist after repositioning. Figure 5A In , workspace 500 may initially contain multiple nodes, including nodes 50, 51, 52, and 53. Subsequently, new node 54 may be added to workspace 500, such as Figure 5B . A user may add a new node 54 to a location where there is not enough space for the new node 54, thereby creating an overlap with one or more of the existing nodes 50, 51, 52, and 53. The modeling application may detect the overlap(s) and may reposition the nodes based on the node distribution and / or number of connection hops between the new node 54 and each of the overlapping existing nodes 50, 51, 52, and 53. Figure 5CThe relocated nodes 50, 51, 52 and 53 are depicted in FIG. Figure 5C , the repositioning of nodes may not completely eliminate the overlap(s) in the workspace 500. In such cases, the modeling application may perform additional operations to eliminate the overlap(s), such as by rescaling or shrinking certain nodes in the workspace 500. The rescaling operation is explained in more detail below.

[0042] Reference Figure 3 At step 350, the modeling application may shrink (i.e., rescale) the set of nodes until there is no overlap. As explained above, the set of nodes may include one or more nodes that overlap with the new node, as well as the new node that is added to the workspace. The set of nodes may further include one or more other nodes that do not overlap with the new node. In general, the set of nodes may be shrunk to a point in time when there is no overlap between the nodes, and such rescaling may be performed based on the current scale and / or size of each node within a predetermined distance of overlap. The parameters defining the local area in which the nodes to be rescaled are located may be configured by a developer or administrator of the modeling application. In some embodiments, a pair of nodes may still be considered to overlap when the rectangular windows of a pair of nodes merely "touch" each other, meaning that the nodes are placed exactly adjacent to each other and one node does not necessarily obscure a portion of the other node. In such a case, the set of nodes may be shrunk to a point in time when a certain distance or gap is reached between the nodes to allow the connection between the nodes to be easily identifiable by clearing the area just outside the periphery of each node. The exact distance or amount / size of the gap required between two nodes that will be considered non-overlapping may depend on the size of the various graphical user interface (GUI) elements used in the node editor.

[0043] In an alternative or additional embodiment, the set of nodes may be rescaled based on a node density map of the workspace. The node density map may be generated based on the location and density / weight of each node included in the workspace. The effective density or weight of the node may be calculated based on the size and current scale of the node. Thus, each node may add a portion of the density / weight to the total density / weight associated with the workspace or a portion of the workspace. Fig. 7A An exemplary self-adjusting workspace 700 including a plurality of nodes is shown, and Figure 7B Shows the corresponding Fig. 7A. In areas where nodes are densely populated (which can be identified from the node density graph), the nodes can be reduced to a relatively smaller size than in areas where the nodes are more sparsely populated or dispersed. In general, the scale or size of a node can be inversely proportional to the node density or weight associated with the local area around the node (e.g., overlapping neighbors, areas within a predetermined distance from the node / overlap). The parameters defining the local area of ​​a node can be configured by a developer or administrator of the modeling application.

[0044] It should be noted that the area surrounding the nodes to be repositioned may be within a first predetermined distance from the overlapping points detected at step 320, and the area surrounding the nodes to be rescaled may be within a second predetermined distance from the overlapping points detected at step 340. In one embodiment, the first predetermined distance and the second predetermined distance may be the same. In other embodiments, the first predetermined distance and the second predetermined distance may be different. As explained above, a developer or administrator may configure the parameters that define the area in which there are nodes to be repositioned or rescaled.

[0045] To prevent differences in node scale when using the node editor, which can be irritating to an end user, the modeling application can adjust the scale as the user pans so that the nodes in the user's field of view are at the same scale. In one embodiment, the action of scaling the nodes to the same scale can be performed by the modeling application in response to determining that the user is scrolling the workspace (i.e., in response to the user zooming in on a particular area of ​​the workspace). In some embodiments, the actions of translating (e.g., zooming in) and scaling the nodes to the same scale can be performed automatically by the modeling application. As an example, Fig. 6A An exemplary self-adjusting workspace 600 is shown when the view of the workspace is panned outward to show all nodes. Notably, when the view is fully panned outward, the nodes may be shown at their true scale, all or some of which may represent any adjustments made when new nodes are added to the workspace. However, a user may only be interested in a subset of nodes at a particular point in time that are in close proximity to the new node or any nodes that the user may be interested in. For example, when a user adds node 64, the user may be interested in surrounding nodes 60, 61, 62, 63, and 65 because one or more of those nodes are likely to be connected to new node 64. Therefore, the modeling application may be configured to adjust the view to zoom in on nodes 60, 61, 62, 63, 64, and 65 when new node 64 is added to the workspace and nodes proximate to new node 64 are rescaled. The area to which the view containing nodes 60, 61, 62, 63, 64, and 65 can be adjusted is shown in FIG. Fig. 6A Shown in FIG. 6 is a region of interest 650 . Figure 6BAn adjusted view of an exemplary self-adjusting workspace 600 is shown, for example, when a new node is added. As explained above, the modeling application can adjust the view to zoom in on the region of interest 650 containing nodes 60, 61, 62, 63, 64, and 65. In addition to zooming in, the modeling application can also resize the nodes 60, 61, 62, 63, 64, and 65 to their pre-zoomed size in order to maintain the nodes at the same scale for user convenience and improved workflow. Thus, nodes 60, 61, 62, 63, 64, and 65 are zoomed in. Figure 6B If the user wants to view or manipulate nodes that are outside of the area of ​​interest 650, the user may be able to pan outward to view the entire workspace 600, or a portion of the workspace 600 that is larger than the area of ​​interest 650, either of which may show the nodes at their true scale depending on predefined specifications.

[0046] Reference again Figure 3 , in order to refer to the above Figure 6A-6B The same scale as explained above is used to maintain the nodes that the user may be interested in. Once the group of nodes is reduced at step 350, the modeling application can adjust the view of the workspace at step 360 to visually maintain the size of the group of nodes before zooming. The view can be adjusted by zooming in on nodes that are closely adjacent to the new node, which may be the user's area of ​​interest. The parameters that define the degree to which the view is zoomed in or the area of ​​interest to which the view is adjusted can be configured by the developer or administrator of the modeling application. When adjusting the view, the nodes visible in the adjusted view can also be adjusted to their node size before zooming. In one embodiment, the adjusted view can cover the overlapping neighbors determined at step 330. In other embodiments, the adjusted view can cover an area larger than the overlapping neighbors, or an area smaller than the overlapping neighbors. Therefore, the adjusted view can include nodes outside the overlapping neighbors, and the nodes outside the overlapping neighbors can also be scaled back to their node size before zooming. At step 350, the node size before zooming of the node can be determined based on the multiplicative inverse of the scale change. If the user wants to view or manipulate nodes that are outside the area of ​​interest represented by the adjusted view, the user may be able to pan outward to view the entire workspace or a portion of the workspace that is larger than the area of ​​interest, either of which may show the nodes at their true scale.

[0047] The embodiments of the present disclosure and all functional operations described in this specification may be implemented in digital electronic circuits, or in computer software, firmware or hardware (including the structures disclosed in this specification and their structural equivalents), or in a combination of one or more of them. The embodiments of the present disclosure may be implemented as one or more computer program products, such as one or more modules of computer program instructions encoded on a computer-readable medium, for execution by a data processing device or for controlling the operation of the data processing device. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a material combination that implements a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" covers all devices, equipment and machines for processing data, including, by way of example, a programmable processor, a computer or multiple processors or computers. In addition to hardware, the device may include code that creates an execution environment for the computer program in question, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagation signal is a non-naturally generated signal, such as a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device.

[0048] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple collaborative files (e.g., files storing one or more modules, subroutines, or code portions). A computer program may be deployed to execute on one computer or on multiple computers located in one location or distributed across multiple locations and interconnected by a communication network.

[0049] The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by special purpose logic circuits, and the apparatus can also be implemented as special purpose logic circuits, such as FPGAs (field programmable gate arrays) or ASICs (application specific integrated circuits).

[0050] By way of example, processors suitable for executing computer programs include both general-purpose and special-purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include or be operatively coupled to one or more mass storage devices (such as magnetic disks, magneto-optical disks, or optical disks) for storing data, to receive data from or transfer data to the one or more mass storage devices, or both. However, a computer need not have such a device. In addition, a computer may be embedded in another device (e.g., a tablet computer, a mobile phone, a personal digital assistant (PDA), a mobile audio player, a global positioning system (GPS) receiver, to name just a few examples). Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, by way of example: semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0051] To provide interaction with a user, embodiments of the present disclosure may be implemented on a computer having a display device, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user, and a keyboard and a pointing device, such as a mouse or trackball, through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including sound, voice, or tactile input.

[0052] Embodiments of the present disclosure may be implemented in a computing system that includes a back-end component (e.g., as a data server), or includes a middleware component (e.g., an application server), or includes a front-end component (e.g., a client computer with a graphical user interface or a web browser through which a user can interact with an implementation of the present disclosure), or includes any combination of one or more such back-end, middleware, or front-end components. The components of the system may be interconnected by any digital data communication form or medium (e.g., a communication network). Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), such as the Internet.

[0053] A computing system may include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The relationship of client and server arises in view of computer programs running on the respective computers and having a client-server relationship to each other.

[0054] Although this specification contains many details, these details should not be interpreted as limitations on the scope of the present disclosure or the scope that may be claimed, but rather as descriptions of specific features of specific embodiments of the present disclosure. Certain features described in the context of separate embodiments in this specification may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments. In addition, although features may be described above as working in certain combinations, and even initially claimed as such, one or more features from the claimed combination may be deleted from the combination in some cases, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.

[0055] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or requiring that all illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Claims

1. A computer-implemented method for automatically adjusting a workspace comprising a plurality of nodes for a continuous workflow, the method comprising: Receive new nodes in the workspace; determining that the new node overlaps with one or more nodes; repositioning a set of nodes within a predetermined distance of overlap, the set of nodes including the new node and the one or more nodes; determining that the new node still overlaps with the one or more nodes; determining a weight of each node within a second predetermined distance of the overlap, wherein the weight of the node is based on a density map of the node, and the weight of the node is calculated based on a size and a current scale of the node; shrinking each node in the set of nodes based on the weight until there is no overlap; as well as The view of the workspace is adjusted to visually maintain the pre-scaling relative node sizes of the new node and each of the one or more nodes. 2 . The computer-implemented method of claim 1 , wherein the set of nodes further comprises one or more other nodes. 3 . The computer-implemented method of claim 1 , wherein the workspace comprises a workspace of a node editor of an object modeling application. The computer-implemented method of claim 1 , wherein each of the plurality of nodes is associated with one or more attributes of an object. The computer-implemented method of claim 1 , wherein the repositioning is based at least in part on distances between the set of nodes. 6 . The computer-implemented method of claim 1 , wherein repositioning is based at least in part on a number of connection hops between the new node and each of the one or more nodes.

7. The computer-implemented method of claim 1 , wherein scaling further comprises: determining the size of each node within a second predetermined distance of overlap; as well as Scaling is performed based on the size of each node within a second predetermined distance of overlap.

8. The computer-implemented method of claim 1, wherein the predetermined distance of overlap comprises a circular area extending from a center point of the overlap, the radius of the circular area being at least twice a size of at least one of the new node and the one or more nodes.

9. The computer-implemented method of claim 1 , further comprising: Make sure the workspace is being scrolled; as well as In response to determining that the workspace is being scrolled, the view of the workspace is adjusted to visually maintain a pre-zoom size of the set of nodes, wherein the pre-zoom size is a size of the set of nodes before being zoomed out.

10. The computer-implemented method of claim 9, wherein adjusting comprises: Zoom in on an area of ​​interest; as well as The set of nodes is displayed at the pre-zoomed size.

11. A system comprising: one or more processors; One or more non-transitory processor-readable storage devices including instructions that, when executed by the one or more processors, cause the one or more processors to perform operations for automatically adjusting a workspace including a plurality of nodes for a persistent workflow, the operations comprising: Receive new nodes in the workspace; determining that the new node overlaps with one or more nodes; repositioning a set of nodes within a predetermined distance of overlap, the set of nodes including the new node and the one or more nodes; determining that the new node still overlaps with the one or more nodes; determining a weight of each node within a second predetermined distance of the overlap, wherein the weight of the node is based on a density map of the node, and the weight of the node is calculated based on a size and a current scale of the node; reducing the set of nodes based on the weights until there is no overlap; and The view of the workspace is adjusted to visually maintain the pre-scaling relative node sizes of the new node and each of the one or more nodes.

12. The system of claim 11, wherein the set of nodes further comprises one or more other nodes.

13. The system of claim 11, wherein the workspace comprises a workspace of a node editor of an object modeling application.

14. The system of claim 11, wherein the repositioning is based at least in part on distances between the set of nodes.

15. The system of claim 11, wherein the relocation is based at least in part on a number of connection hops between the new node and each of the one or more nodes.

16. The system of claim 11, wherein scaling further comprises: determining the size of each node within a second predetermined distance of overlap; as well as Scaling is performed based on the size of each node within a second predetermined distance of overlap.

17. The system of claim 11, wherein the predetermined distance of overlap comprises a circular area extending from a center point of the overlap, the radius of the circular area being at least twice a size of at least one of the new node and the one or more nodes.

18. The system of claim 11, the operations further comprising: The view of the workspace is adjusted to visually maintain a pre-zoom size of the set of nodes, wherein the pre-zoom size is a size of the set of nodes before being zoomed out.

19. The system of claim 18, wherein adjusting comprises: Zoom in on an area of ​​interest; as well as The set of nodes is displayed at the pre-zoomed size.

20. One or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors, cause the one or more processors to perform operations for automatically adjusting a workspace comprising a plurality of nodes for a persistent workflow, the operations comprising: Receive new nodes in the workspace; determining that the new node overlaps with one or more nodes; repositioning a set of nodes within a predetermined distance of overlap, the set of nodes including the new node and the one or more nodes; determining that the new node still overlaps with the one or more nodes; determining a weight of each node within a second predetermined distance of the overlap, wherein the weight of the node is based on a density map of the node, and the weight of the node is calculated based on a size and a current scale of the node; reducing the set of nodes based on the weights until there is no overlap; as well as The view of the workspace is adjusted to visually maintain the pre-zoom relative node size of each of the set of nodes.