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 597243 - delete key on a clip in the source list should remove it only if the timeline is not focused
delete key on a clip in the source list should remove it only if the timeline...
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: User interface
0.13.3
Other Linux
: Normal major
: 0.13.4
Assigned To: Pitivi maintainers
Pitivi maintainers
: 602893 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-03 22:11 UTC by Jean-François Fortin Tam
Modified: 2010-02-17 08:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2009-10-03 22:11:44 UTC
The fix for bug #595402 caused a regression. As soon as you hit delete to remove a clip from the timeline, it is also removed from the source list, even if you were working on the timeline (and thus, it was focused). This is dangerous behavior.
Comment 1 Karl Palsson 2009-10-21 00:11:13 UTC
Confirmed.  What makes it worse is that you can't unselect a clip in the clip list, so you have to save, and then reopen to be able to use the delete key to delete objects from the timeline.  (newly opened projects have no clips in the clip list selected, but if you have  just added a clip, it's selected, and there's no way to unselect it that I saw)

And I felt so proud fixing that bug :(
Comment 2 Jean-François Fortin Tam 2010-02-05 23:24:29 UTC
Changing component, raising the severity as it can cause data/work loss and is generally dangerous.
Comment 3 Jean-François Fortin Tam 2010-02-06 00:42:38 UTC
*** Bug 602893 has been marked as a duplicate of this bug. ***
Comment 4 Jean-François Fortin Tam 2010-02-10 13:54:36 UTC
Karl, are you able to make a new patch that would fix this?
Comment 5 Jean-François Fortin Tam 2010-02-16 14:12:02 UTC
I can't reproduce the problem anymore with the git version, I think it was fixed when Stephen's "icon view" branch was merged. I'm not sure I should reopen bug #595402 because I personally consider it to be a dangerous feature, and because it can be done with right-click or using the toplevel menus...
Comment 6 antistress 2010-02-17 00:26:11 UTC
as Karl Palsson said on Bug 595402 : "if delete in the timeline deletes a clip, there's no reason that delete on the source list shouldn't delete the clip."
If the fix can be properly implemented then there is no reason to not fix it
Comment 7 Jean-François Fortin Tam 2010-02-17 02:30:00 UTC
> "if delete in the timeline deletes a clip,
> there's no reason that delete on the source list shouldn't delete the clip."


My reasoning is the following:

- We already have a popup menu and the toplevel menus to do that.

- The user has to be 160% sure what is focused (timeline vs source list), which is not something I consider visually obvious and safe.

- Removing a clip from the timeline has only local consequences; deleting from the source list is an action with *global consequences*: it deletes every instance of the clip you had in the timeline.

- Removing something from the timeline is an action you do *often* in an editing workflow (think "remove the audio part of a clip after unlinking" or "remove leftovers of a split operation", for example), thus warranting the keyboard shortcut. Deleting something from a project entirely is not something that is expected to be done often. And if you want to "clean up" the project fast, then it's bug #583254 instead.

As an analogy, you don't see a shortcut key to remove contacts from your pidgin/empathy buddy list, you can only do it with the menus... that's because it's dangerous and not supposed to be used often.
Comment 8 antistress 2010-02-17 08:35:53 UTC
"emoving a clip from the timeline has only local consequences; deleting from
the source list is an action with *global consequences*: it deletes every
instance of the clip you had in the timeline"
i didn't know about that... does pitivi show a warning about that ? i think it should