Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI: (low) Behavior categories - Rename - Oddities #455

Open
kaltinril opened this issue Jan 2, 2025 · 1 comment
Open

UI: (low) Behavior categories - Rename - Oddities #455

kaltinril opened this issue Jan 2, 2025 · 1 comment
Labels

Comments

@kaltinril
Copy link
Collaborator

This is just a "Feeling" ticket.

There is 1 issue though..................
The one issue is that renaming a category, should propagate to the components, or, at least, do what happens when you disassociate and reassociate it.

Feelings:

  1. Renaming a category on a Behavior does not populate the rename down to the components.
  2. Upper and Lower are considered different behaviors (Cat1 and cat1 and CAT1 are all different categories)
  3. Creating a new category will finally populate the renamed category over to the component
  4. Renaming a category doesn't move the states that were on the category over to the new category

In short, it feels weird that the Categories and their states that come from a Behavior, are not "linked" to them for life. Instead, it seems like they are simply a cookie cutter, that you "stamp" the component with, but you haven't baked the cookie (Category/State) yet, so you can still modify it. Which is odd.

The fact you can have lower/upper case is weird

The fact

UuSNl2dgMX.mp4
@kaltinril kaltinril added the bug label Jan 2, 2025
@vchelaru
Copy link
Owner

vchelaru commented Jan 2, 2025

I agree with the comments here. I don't want to start working on this one yet because it's a bigger task, and related to this issue related to renaming:

#305

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants