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
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
The appearance folder is perfect except for one thing. I'd like to see categories separating outfits by category. The user would create the category and then would have the option of saving the outfits in which category that it belongs in. For instance:
Appearance -> Cheerleading -> Group Name -> Outfit Name -> Folder Contents
Appearance -> Star Trek -> Group Name -> Outfit Name -> Folder Contents
Appearance -> Professional -> Group Name -> Executive Boss -> Folder Contents
....
This would save a lot of scrolling and one could select an outfit straight from a category. Otherwise, each category is collapsed to reduce the screen clutter.
Why is this feature important to you? How would it benefit the community?
If there are others like me, many people have many fits. This takes time to scroll down the screen until one finds the correct outfit for the setting. Why not split it into a main category and then subdivide it by 2 or three sub-categories to ensure that it is less scrolling. One could go right to it w/out a hassle.
{
'Business Unit': ['Platform'],
'Date of First Response': '2017-01-23T15:43:51.705-0600',
'How would you like the feature to work?': "The appearance folder is perfect except for one thing. I'd like to see categories separating outfits by category. The user would create the category and then would have the option of saving the outfits in which category that it belongs in. For instance:\r\n\r\nAppearance -> Cheerleading -> Group Name -> Outfit Name -> Folder Contents\r\nAppearance -> Star Trek -> Group Name -> Outfit Name -> Folder Contents\r\nAppearance -> Professional -> Group Name -> Executive Boss -> Folder Contents\r\n....\r\n\r\nThis would save a lot of scrolling and one could select an outfit straight from a category. Otherwise, each category is collapsed to reduce the screen clutter.",
'ReOpened Count': 0.0,
'Severity': 'Unset',
'Target Viewer Version': 'viewer-development',
'Why is this feature important to you? How would it benefit the community?': 'If there are others like me, many people have many fits. This takes time to scroll down the screen until one finds the correct outfit for the setting. Why not split it into a main category and then subdivide it by 2 or three sub-categories to ensure that it is less scrolling. One could go right to it w/out a hassle.',
}
The text was updated successfully, but these errors were encountered:
I was unaware that was once a feature. I'd like it back with the bugs fixed if all possible. I myself have tons of outfits and a lot of times takes minutes finding the correct one. I have to temporarily use a number system and queues at the front of the outfits to make it easier but still takes time.
How would you like the feature to work?
The appearance folder is perfect except for one thing. I'd like to see categories separating outfits by category. The user would create the category and then would have the option of saving the outfits in which category that it belongs in. For instance:
Appearance -> Cheerleading -> Group Name -> Outfit Name -> Folder Contents
Appearance -> Star Trek -> Group Name -> Outfit Name -> Folder Contents
Appearance -> Professional -> Group Name -> Executive Boss -> Folder Contents
....
This would save a lot of scrolling and one could select an outfit straight from a category. Otherwise, each category is collapsed to reduce the screen clutter.
Why is this feature important to you? How would it benefit the community?
If there are others like me, many people have many fits. This takes time to scroll down the screen until one finds the correct outfit for the setting. Why not split it into a main category and then subdivide it by 2 or three sub-categories to ensure that it is less scrolling. One could go right to it w/out a hassle.
Links
Related
Duplicates
Original Jira Fields
The text was updated successfully, but these errors were encountered: