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 603107 - keyframes are hard to manipulate near trimming handles/clips edges
keyframes are hard to manipulate near trimming handles/clips edges
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: User interface
Git
Other Linux
: Normal normal
: 0.13.4
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-27 04:27 UTC by Jean-François Fortin Tam
Modified: 2010-01-22 23:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2009-11-27 04:27:23 UTC
Currently, keyframes 
- are contained "inside" the boundaries of the clips (ie: they can't "bleed" over the border and outside the clip's bounding box)
- are shown under the trimming handles

This is problematic because it's basically impossible to manipulate the first and last keyframe.

A potential way to work around this would be to layer the curves+keyframes "on top" of trimming handles, and making the keyframes/curves' hitbox prioritized over the trimming handle's hitbox (since it's large enough anyway). Thus if we can see and click the keyframe at the end of a clip even though the trimming handle is shown under, then we can do manipulations such as fades much more easily (at least until we have "real" transitions and bug #579230 cornered).
Comment 1 Brandon Lewis 2010-01-22 23:45:56 UTC
commit 660aab6c93230aa25b16eafa29f8c3a966d14ba9
Author: Brandon Lewis <brandon_lewis@alum.berkeley.edu>
Date:   Tue Jan 5 10:52:49 2010 -0800

    curve.py, trackobject.py: fix curve hitbox detection issues
    curve.py: make keyframes larger again
    
    closes bugs 603425, 603107