| Summary: | Clip Properties > File info, a fixed and more easy to read order. | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | Gabriel Gazzán <gabcorreo> |
| Component: | User Interface & Miscellaneous | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | berndmj |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | File Info order | ||
...ok, as always the Preview feature of this text editor is playing games, so forgive some horizontal misalignment of values, here and there `:) This intended to be in "Whishlist" category. Forgot to check it before sending (and couldn't find a way to change it later), sorry. Thanks for the suggestion! Makes a lot of sense. Git commit 37093b3329fec2a4b208c0313af3edefc34cfa76 by Jean-Baptiste Mardelle. Committed on 18/11/2025 at 10:34. Pushed by mardelle into branch 'release/25.12'. Fixed order for clip properties, add separator between categories M +8 -5 src/bin/bin.cpp M +1 -0 src/bin/bin.h M +1 -1 src/core.cpp M +1 -1 src/mainwindow.cpp M +1 -1 src/mainwindow.h M +73 -40 src/mltcontroller/clippropertiescontroller.cpp M +12 -0 src/mltcontroller/clippropertiescontroller.h https://invent.kde.org/multimedia/kdenlive/-/commit/37093b3329fec2a4b208c0313af3edefc34cfa76 🐐✨ |
Created attachment 186834 [details] File Info order Currently, in Clip Properties widget, File Info tab, the order in which the different data obtained from the file is presented in an alphabetical order. This leads it to be: 1. Harder to read. As information is not following any logical sequence of appearance. 2. Not in a stable location. For each language, the alphabetical order of parameter names will be different, so the info will potentially be all over the place, when users share screenshots in forums. Leading to potential confusion. (A screenshot is attached, showing as an example, the current differences in location between English and Spanish) So, I think it could be a good thing to present this information in a more structured an fixed way. Something similar to the following: ------------------------------------------ File size: 63 MiB ------------------------------------------ Video streams: 1 Frame size: 1920x1080 Pixel aspect ratio: 1.000 Pixel format: yuv422p10le Colorspace: ITU-R BT.709 Frame rate: 25 Scanning: Progressive Video codec: H.264 B frames: No Video bitrate: 31000 Kb/s ------------------------------------------ Audio streams: 4 Audio channels: 2 Audio frequency: 48000 Hz Audio codec: PCM signed 16-bit Audio bitrate: 1536 Kb/s ------------------------------------------