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

Removing track causes reset of all track titles #321

Closed
PanderMusubi opened this issue Sep 8, 2016 · 8 comments
Closed

Removing track causes reset of all track titles #321

PanderMusubi opened this issue Sep 8, 2016 · 8 comments
Labels
🐞 bug A bug, error, or breakage of any kind

Comments

@PanderMusubi
Copy link

Removing track ( in this case Track 0 at the bottom) causes all custom track titles to get reset to Track 0, Track 1, etc. Please fix this so that custom track titles are maintained after deleting a track.

@ghost ghost added the 🐞 bug A bug, error, or breakage of any kind label Mar 14, 2017
@DylanC
Copy link
Collaborator

DylanC commented Aug 22, 2017

@PanderMusubi - Is this still an issue for you in newer versions of OpenShot?

@DylanC
Copy link
Collaborator

DylanC commented Oct 9, 2017

Confirmed in v2.4.0 and the daily build.
OpenShot-v2.4.0-1-g8a71c3d-55-646-x86_64

@peanutbutterandcrackers
Copy link
Contributor

I can confirm that this exists even in v2.4.1 - the daily build (Mar 9 2018). However, I figured out that if I do Ctrl + Z, the custom names come back. So, apparently, OpenShot is over-doing a few steps.

Same/similar issue in #1302

@DylanC
Copy link
Collaborator

DylanC commented Mar 9, 2018

@peanutbutterandcrackers - Excellent information! Thanks.

@peanutbutterandcrackers
Copy link
Contributor

@DylanC - I hope this will be resolved soon. You're most welcome!

@DylanC
Copy link
Collaborator

DylanC commented May 8, 2018

@PanderMusubi - Hi there, can you try a daily build? This fix went in and should be available to you.

@PanderMusubi
Copy link
Author

@DylanC I'm not using it at the moment.

@DylanC
Copy link
Collaborator

DylanC commented May 8, 2018

@PanderMusubi - No problem. Its been confirmed as fixed anyway in #454

@DylanC DylanC closed this as completed May 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug A bug, error, or breakage of any kind
Projects
None yet
Development

No branches or pull requests

3 participants