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 776925 - Fixing default widget widths
Fixing default widget widths
Status: RESOLVED DUPLICATE of bug 689438
Product: easytag
Classification: Other
Component: general
2.4.x
Other Linux
: Normal normal
: 2.4
Assigned To: EasyTAG maintainer(s)
EasyTAG maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-01-06 01:01 UTC by Frank
Modified: 2017-01-06 08:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
[1] (118.53 KB, image/png)
2017-01-06 01:01 UTC, Frank
Details
[2] (109.56 KB, image/png)
2017-01-06 01:02 UTC, Frank
Details
[2] (109.56 KB, image/png)
2017-01-06 01:03 UTC, Frank
Details
[3] (476.35 KB, image/png)
2017-01-06 01:04 UTC, Frank
Details

Description Frank 2017-01-06 01:01:35 UTC
Created attachment 342987 [details]
[1]

The default widths are suboptimal, so I need to resize all three main panes every time I start the application. These widths should be fixed and changes saved. I appended three examples:
1. The CD-Tag should be auto-sized, if e.g. „01/02“ is contained (until a certain maximum).
2. With other themes, more boxes are too small (Year, CD, CD-Tracks) and should be auto-expanded.
3. With default settings, the tree pane is far too wide, while the Tag pane should be auto-sized depending on the content (until a certain maximum). The main pane should eat up all remainung space. The tree pane should by default have the width of the file system tree and expand until a certain maximum if more folders are opened and the tree thus getting wider.
Comment 1 Frank 2017-01-06 01:02:09 UTC
Created attachment 342988 [details]
[2]
Comment 2 Frank 2017-01-06 01:03:30 UTC
Created attachment 342990 [details]
[2]
Comment 3 Frank 2017-01-06 01:04:55 UTC
Created attachment 342992 [details]
[3]
Comment 4 David King 2017-01-06 08:47:36 UTC
This is a duplicate of bug 689438 and also bug 739701.

*** This bug has been marked as a duplicate of bug 689438 ***