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

Behavior dirty state not working for behaviors not created in that scene #657

Open
BrennaCourtney opened this issue Jul 28, 2022 · 0 comments
Labels
bug 🐛 Something isn't working

Comments

@BrennaCourtney
Copy link
Contributor

BrennaCourtney commented Jul 28, 2022

Describe the bug
When a behavior is added to a scene it was not created in, dirty state acts up.

behavior_form_editing.mp4

"Driver Front Door Open" was created in another scene and added to this one, while "wing L upper status" was created in this scene. As you can see from the video, making no changes to the first behavior prompts dirty state warning, while making no changes to the second one does not.

To Reproduce
Steps to reproduce the behavior:

  1. Go to an existing scene (or create a new one).
  2. Create a new behavior in the scene.
  3. Add a different, existing behavior that was created in a different scene.
  4. Enter the edit form for each behavior, but don't make any changes.
  5. Observe the different behavior.

Expected behavior
Behaviors created in other scenes but added to the current one should result in the same dirty state conditions as behaviors created in that scene (i.e. entering edit behavior form and making no changes should allow you to navigate away without a warning).

Screenshots
See above

Browser (please complete the following information):

  • Chrome

Additional context
May be related to recent behavior context overhaul

@BrennaCourtney BrennaCourtney added the bug 🐛 Something isn't working label Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant