You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes. Manual Grouping is not very intuitive right now. Currently, if I have created a group of multiple regions, if I cut (Ctrl + X) a parent region by mistake, the entire group is broken (thankfully, I can undo this with Ctrl + Z). I am not able to form groups very easily, if I have a long list of regions, I have to drag some element all the way from bottom to my group.
Describe the solution you'd like
I feel that we should be able to cut (Ctrl + X) a rectangle/polygon region and paste it inside another region (by selecting it) to start/continue grouping. Also, when we cut an element which has some children, then it should be cut and pasted with all its children intact instead of breaking up the grouping, this would help in case I am creating a hierarchy where I want a whole group to go and sit inside another group (right now I have to drag the first group to place it inside another).
Describe alternatives you've considered
I have considered tagging relations in multi-page documents, however, the arrows do not render when doing this. I have noticed on some other tools such as labelbox, they still render the arrow for multi-page relations by making an arrow from the starting node to page boundary (containing reference to the ending node) and then on the ending node's page, there is a continued arrow from page boundary (containing reference to the starting node) to ending node.
Therefore, to bypass the multi-page relations not working. I tried grouping the inter-page elements with relations and started running into above issues.
The text was updated successfully, but these errors were encountered:
HJJ256
changed the title
Make grouping more intuitive
Grouping needs to be more intuitive
Apr 17, 2025
Could you please share any additional details on how you’d expect the paste operation to behave in complex use cases (for example, handling multi-page documents or specific scenarios where preserving grouping is critical)? Any further information will help us fine-tune the solution.
For a multi-page document tagging task, I am trying to use groups for creating a hierarchy of objects tagged on different pages. Currently when I try to cut an object (say, o1) then select another object (say, o2) (which I want as parent) then try to paste o1, it does not go under o2, I would ideally want it to join o2's group. Also let's say I have the group (o2->o1) ready then if I cut o2, it breaks up the group instead of making a cut and paste of the whole group.
Let me know if you have any other specific questions.
Is your feature request related to a problem? Please describe.
Yes. Manual Grouping is not very intuitive right now. Currently, if I have created a group of multiple regions, if I cut (Ctrl + X) a parent region by mistake, the entire group is broken (thankfully, I can undo this with Ctrl + Z). I am not able to form groups very easily, if I have a long list of regions, I have to drag some element all the way from bottom to my group.
Describe the solution you'd like
I feel that we should be able to cut (Ctrl + X) a rectangle/polygon region and paste it inside another region (by selecting it) to start/continue grouping. Also, when we cut an element which has some children, then it should be cut and pasted with all its children intact instead of breaking up the grouping, this would help in case I am creating a hierarchy where I want a whole group to go and sit inside another group (right now I have to drag the first group to place it inside another).
Describe alternatives you've considered
I have considered tagging relations in multi-page documents, however, the arrows do not render when doing this. I have noticed on some other tools such as labelbox, they still render the arrow for multi-page relations by making an arrow from the starting node to page boundary (containing reference to the ending node) and then on the ending node's page, there is a continued arrow from page boundary (containing reference to the starting node) to ending node.
Therefore, to bypass the multi-page relations not working. I tried grouping the inter-page elements with relations and started running into above issues.
The text was updated successfully, but these errors were encountered: