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 738830 - Autosizing columns has side-effect of selecting all rows
Autosizing columns has side-effect of selecting all rows
Status: RESOLVED FIXED
Product: easytag
Classification: Other
Component: general
2.2.x
Other Linux
: Normal normal
: 2.2
Assigned To: EasyTAG maintainer(s)
EasyTAG maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-10-19 21:28 UTC by J.B. Nicholson
Modified: 2014-10-20 08:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description J.B. Nicholson 2014-10-19 21:28:28 UTC 
In version 2.2.4 you can see this side-effect by doing the following:

1. Open a directory with multiple audio files in EasyTag. The first audio file is automatically selected and no other audio file is automatically selected.

2. Double-click the column separator between two neighboring columns and EasyTag will autosize the left column (this is correct behavior) and EasyTag will also select all audio files (this is the side-effect).

I'm not aware of other applications automatically selecting all editable objects when one autosizes the columns, so this behavior sticks out as odd.

This behavior might exist in other OSes where EasyTag runs, but I've only tried this on GNU/Linux so that's where I marked this ticket.
Comment 1 J.B. Nicholson 2014-10-19 21:55:14 UTC 
One small correction: if you pick a folder that has multiple subfolders where each subfolder has audio files in it, double-clicking a column separator will select all audio files in the topmost folder. It's not clear to me why one would want this behavior connected to resizing a column.

And just to be clear: I think that the audio file selection (row selection) should remain undisturbed when one resizes columns.
Comment 2 David King 2014-10-20 08:27:42 UTC 
Thanks for the bug report. I fixed this in the master and easytag-2-2 branches as 3fbdffab187351818ec81cf7b7853b1b8f66c741 and 195e0cf176dee6a414b9b32e676c8178b54c8af8. The fix will be included in the next release.