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

problem on the scene selector #207

Closed
irwant opened this issue Jul 6, 2024 · 3 comments
Closed

problem on the scene selector #207

irwant opened this issue Jul 6, 2024 · 3 comments

Comments

@irwant
Copy link

irwant commented Jul 6, 2024

this issue about the scene selector not working properly.
try to make 2 scene and change the scene on the scene selector canvas. when changed to the scene B, scene on the timeline not changed automatically to scene B because active cursor not on the canvas but on the timeline. check my video attachment.

frictions.mp4
@irwant
Copy link
Author

irwant commented Jul 6, 2024

I don't know this is need to change, because this is important when linking scene A to scene B. and if the link scene A need any change keyframe for quick access, just simple to change scene selector on the timeline or split timeline. I think this is not a big problem, just need a documentation of this feature.

@rodlie
Copy link
Member

rodlie commented Jul 6, 2024

The viewer is not "connected" to the timeline in regards to scenes, changing scene in the viewer will not change anything in the timeline, this is because you can have multiple amount of timelines and viewers (you can also have multiple viewers/timelines for one scene).

just need a documentation of this feature

Agree, a lot of things need documentation (we don't have any). This project is mostly maintained and developed by one person in their spare time, so there are limits to what can be done.

@rodlie
Copy link
Member

rodlie commented Aug 17, 2024

Will close this, everything works as intended. Can possible be improved or changed in the future, but that's another discussion.

This feature will of course need to be documented #208

@rodlie rodlie closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants