GNOME Bugzilla – Bug 674138
no "import files" button as mentioned in instruction header of left file box
Last modified: 2012-09-25 20:30:37 UTC
Maybe it is just the German translation... but the help text above the left file box is confusion and points to a non-existent button. It says one should use the "import files" ("Dateien importieren") button to add media to the project - but there is no such button visible. There is a button in the toolbar that is named "Mediendaten zu Ihrem Project hinzufügen" ("add media data to your project"). Maybe this is meant to be the mentioned button but shouldn't the shown instruction then name it correctly? There also is a button called "import files" in the context menu of the file box - but as pitivi aims to be very easy with high usability the help only should refer to visible buttons - or say where to find that button in case it is not visible? I had two people independent from each other who did not know how to start with pitivi because they relied on the instruction and were looking for the mentioned button near the box and could not find it. Maybe it would have been easier for them if the instruction would not have mentioned that button at all because then they would have presumably clicked on the button in the toolbar. It is a minor gui (or translation) bug for me - but stopped some others from working.
That's strange, starting pitivi 0.15 with "LANG=de_DE.UTF8 pitivi", it seems like the toolbar matches the media library's infobar... and indeed, the english version does use the term "Import Files..." in both places.
Created attachment 212086 [details] screenshot Does what you see match this?
Hello Jean, taking over from here. Hallo Janet, welche Version von pitivi nutzt du? In einer aktuellen Version sehe ich das Problem nicht.
Created attachment 212097 [details] Bildschirmfoto
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Sorry, I lost track of this report. Yes, the issue was solved after upgrading to a newer version. Thanks for caring.