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 611856 - Ability to enter custom framerates manually
Ability to enter custom framerates manually
Status: RESOLVED OBSOLETE
Product: pitivi
Classification: Other
Component: Rendering
Git
Other Linux
: Normal enhancement
: 0.14
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2010-03-05 01:30 UTC by Jean-François Fortin Tam
Modified: 2010-12-10 18:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
proof of concept (1.23 KB, text/x-python)
2010-03-05 01:30 UTC, Jean-François Fortin Tam 		Details

Description Jean-François Fortin Tam 2010-03-05 01:30:43 UTC 
Created attachment 155271 [details]
proof of concept

Replace the combobox framerate widget by a comboboxentry widget to allow the user to input custom framerates, in decimal (ex: 12, 12.0, 12.00, 29.97) or ratio (ex: 3000:1001) mode.

Brandon had some related work started in his rendering cleanup branches, if memory serves right. We had a nice debate on 2009-10-22 about the "it should parse decimal framerates, and also parse the handful of industry-standard decimal framerate approximations" (I can provide the chat log if anyone cares).

That day, I ended up writing a proof of concept python script illustrates what I mean (attached to this bug report), you just have to imagine a comboboxentry instead of the terminal staring at you.