https://bugs.kde.org/show_bug.cgi?id=502091
--- Comment #21 from Bernd <bern...@yahoo.com> --- (In reply to Gabriel Gazzán from comment #20) > Which rises your very valid question: > > Why would I need a modifier for this? Why not make track separation lines > > sensitive areas from the very start? > > Well (and that's debatable, of course, but) the main reason I imagined the > use of a modifier key for track insertion between existent tracks, was to > avoid the timeline to become a "Xmas tree" every time the user drags a clip > to a track for other purposes. > Dragging a clip above the top-most track (or bottom-most track) is a very > specific action that I think could trigger the dashed line (or even open > that cool preview, @balooii showed us) without causing noticeable hassle or > being distracting if activated by error, but I guess, having dashed lines or > mini track previews appearing and disappearing as the mouse cursor travels > over each tracks division line could be. > So the solution to avoid that would be that, only when the user "declares an > intention" to do so (by pressing Ctrl) the said dashed lines would be shown. That makes perfect sense. Thanks for thinking this through more than I did. I totally agree that this would irritate the user. So, a drop zone only at the top it is. And as a modifier key I suggest the Special key (Windows, Mac) because CTRL is associated with copying while dragging (which may be introduced later so that you can drag© clips to other locations in the timeline), and SHIFT may be used for locking horizontal or vertical movement. That leaves ALT as a possible modifier but perhaps we want to use this to switch from insert-at-top to insert-at-bottom. -- You are receiving this mail because: You are watching all bug changes.
