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
This might be tricky, and it is debatable that it is needed. I see two approaches:
Cards are grouped by having the same non-unique settings
Cards are grouped by the initial grouping created by the user when adding the resource (I believe this will be easier)
Approach 1 requires the page to search through existing resource cards upon changing/creating a card. If there are similar settings, the changed/created card gets added to the found card (either multi or single).
Approach 2, simply bunch the resource cards together when they are created using the "Number of Instances" option, and always keep them together regardless of their settings.
Approach 1 seems to be a nicer organizational method, but that may depend on what the user wants + it is more tricky to implement.
Approach 2 gives the user more control over how resources are bunched together (in approach 1, they might accidentally set a resource up exactly the same as another resource and be confused when those two get put into a multi-card, but this approach doesn't have that issue, they are in control)
The text was updated successfully, but these errors were encountered:
This might be tricky, and it is debatable that it is needed. I see two approaches:
Approach 1 requires the page to search through existing resource cards upon changing/creating a card. If there are similar settings, the changed/created card gets added to the found card (either multi or single).
Approach 2, simply bunch the resource cards together when they are created using the "Number of Instances" option, and always keep them together regardless of their settings.
Approach 1 seems to be a nicer organizational method, but that may depend on what the user wants + it is more tricky to implement.
Approach 2 gives the user more control over how resources are bunched together (in approach 1, they might accidentally set a resource up exactly the same as another resource and be confused when those two get put into a multi-card, but this approach doesn't have that issue, they are in control)
The text was updated successfully, but these errors were encountered: