Bug 384560 - [Usability] jump next cut in current track only
Summary: [Usability] jump next cut in current track only
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface (show other bugs)
Version: git-master
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-10 12:37 UTC by alberto
Modified: 2021-03-14 15:11 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: Brainstorm+

Attachments
jump cut example (63.58 KB, video/mp4)
2021-03-13 21:36 UTC, farid 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description alberto 2017-09-10 12:37:30 UTC 
Sorry for opening so many bugs. I promise this will be the last one that is not a real bug but wishlist material :)

When you are editing a single track, it should be possible to jumping to next cut in current track only, instead of the next relevant point with alt + arrows

Rationale is that might have a track full of clips, and you are editing another non related track and it makes you move very slowly

Possible solutions:
- mark which tracks should be considered as relevant points
- shortcut to toogle all/current track navigation
- use a different shortcut
Comment 1 ivangretsky 2020-05-17 16:43:32 UTC 
I think it could be a good enhancement too. Maybe only jump on active tracks?
Comment 2 Jean-Baptiste Mardelle 2020-05-20 03:57:23 UTC 
In fact this has been implemented since 20.04. We now only seek to snap points on the active tracks. By default all tracks are active but you can make a track inactive by clicking on it's tag (V1,A2,..) or using shortcuts. Please test and let us know if it works for you.
Comment 3 ivangretsky 2020-05-20 07:51:30 UTC 
Just tested it on Windows on 20.04.01 and it does not work - still snaps to key points on all tracks.
Comment 4 Bug Janitor Service 2020-06-04 04:33:09 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 ivangretsky 2020-06-04 07:56:11 UTC 
Didn't know i need to change the status - no I do)
Comment 6 farid 2021-03-13 21:36:24 UTC 
Created attachment 136653 [details]
jump cut example
Comment 7 farid 2021-03-13 21:37:55 UTC 
(In reply to ivangretsky from comment #3)
> Just tested it on Windows on 20.04.01 and it does not work - still snaps to
> key points on all tracks.

This is implemented, see attachment on how to use.
Comment 8 ivangretsky 2021-03-14 15:11:25 UTC 
(In reply to farid from comment #7)
> This is implemented, see attachment on how to use.

Just tested it out and it works great! Thank you!