forked from OpenNeo/impress
Emi Matchu
578528f468
Specifically, I was looking at the new "Stormy Cloud Kacheek" items, and was surprised to find that, in the outfit editor, they all get grouped under "Markings" (and therefore the UI treats them as mutually-exclusive via hidden radio button and only bolds one at a time), but they aren't actually conflicting because they occupy different zones named "Markings". In this change, we make the zone groups actually just be *by zone* rather than jumbling all of the zones with the same label together; but in most cases, we still keep the same simplified display. In the case of the "Stormy Cloud Kacheek" items though, we now get a few groups: `Glasses`, `Markings (#6)`, and `Markings (#16)`. Glasses is chosen by coincidence because it's the first zone label for that item alphabetically (even though that item also occupies a third "Markings" zone), and then the other two know to disambiguate from each other. There's an opportunity here to cheat things further, like to *intentionally* select items like "Glasses" that are less ambiguous when possible. I'm not aware of enough other cases like this for that to really matter, though, so I'm just leaving it as-is! I tested this a *bit* on other outfits, and everything looked fine at a glance, so I'm just moving forward—but I'll make an announcement to ask people to help take a look! |
||
|---|---|---|
| .. | ||
| support | ||
| index.js | ||
| Item.js | ||
| ItemsAndSearchPanels.js | ||
| ItemsPanel.js | ||
| LayersInfoModal.js | ||
| OutfitControls.js | ||
| OutfitKnownGlitchesBadge.js | ||
| PosePicker.js | ||
| SearchFooter.js | ||
| SearchPanel.js | ||
| SearchToolbar.js | ||
| useOutfitSaving.js | ||
| useOutfitState.js | ||
| useSearchResults.js | ||
| WardrobePageLayout.js | ||
| WardrobePreviewAndControls.js | ||