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
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:
Renaming a category on a Behavior does not populate the rename down to the components.
Upper and Lower are considered different behaviors (Cat1 and cat1 and CAT1 are all different categories)
Creating a new category will finally populate the renamed category over to the component
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
The text was updated successfully, but these errors were encountered:
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:
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:
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
The text was updated successfully, but these errors were encountered: