After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 609518 - Razor at cursor point
Razor at cursor point
Status: RESOLVED DUPLICATE of bug 594389
Product: pitivi
Classification: Other
Component: Timeline
0.13.x
Other Linux
: Normal enhancement
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
: 611200 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-02-10 10:24 UTC by Robert Varnam
Modified: 2010-03-06 04:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert Varnam 2010-02-10 10:24:05 UTC 
Pitivi could become the defacto radid-editing tool on Linux if it had a 'razor at cursor' function.  Pressing a key during playback of the timeline would insert a cut at that timeline point. This would allow clips to be edited very rapidly, without resorting to switching between the preview and the timeline, or the inaccuracies of using the mouse to place the razor point
Comment 1 Jean-François Fortin Tam 2010-02-10 13:28:36 UTC 
What exact version of pitivi are you using? Or are you using pitivi git? (see https://launchpad.net/~rowinggolfer/+archive/pitivi-unstable for pre-built testing packages)

This is already implemented if I'm not mistaken. See http://jeff.ecchi.ca/blog/2009/11/30/move-playhead-on-click-modeless-splitting-full-height-playhead/
Comment 2 Jean-François Fortin Tam 2010-02-10 14:11:54 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 594389 ***
Comment 3 Jean-François Fortin Tam 2010-03-06 04:42:06 UTC 
*** Bug 611200 has been marked as a duplicate of this bug. ***