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

[BUG] Changing the length of a tween using the numeric input field (with keyboard) causes data loss as intermediate keyframes are thrown away #359

Open
nekohayo opened this issue Sep 26, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@nekohayo
Copy link

nekohayo commented Sep 26, 2022

To Reproduce
Steps to reproduce the behavior:

  1. Create a 15-frames-long tween with keyframes at frame no 1, 10
  2. Click on the tween in the timeline
  3. In the inspector sidebar, try to change the length from 15 to 25

Actual behavior
The keyframe at position 10 is lost because when you are typing the new length number, you first type the number "2" before typing number "5", and changes are instant-applied, so in practice it sets the length to 2 and discards any existing keyframe outside that boundary. This is data loss and is super dangerous UX.

Worse, if you click frame 10 and drag the existing item around to "recreate" the keyframe/movement, bug #357 happens!

Expected behavior
Do not ever throw away user data like that.


Tested on Firefox directly on https://www.wickeditor.com/editor/

@nekohayo nekohayo added the bug Something isn't working label Sep 26, 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