Window sizing oddities in "Downloading Package Files" status window

[David D Miller]

When you click the disclosure triangle to show progress of single files, the
window is too narrow to be able to see the filename that's being downloaded at
the same time as the progress meter showing its progress. The window is also
not resizable, so you can't make it wider to accommodate. Also, the window
width seems to "jiggle" a little if a package with a long filename gets added to
the list in the progress window. The content of the listbox is obviously
getting wider (the scrollbar adjusts) but it seems to kick the width of the
window itself by a few pixels as well.

[David D Miller (justdave)]

(this is in hoary, btw)

[Michael Vogt (mvo)]

Thanks for this bugreport. I'll have a closer look soon.

[Martin Kretzschmar (martink)]

I think it's not long list entries that make window width "jiggle," but the
width of the progress bar which itself depends on the length of the text inside.
And that text changes its width whenever the ETA changes.

[Michael Vogt (mvo)]

I fixed this problem in the current development version of synaptic. It will be
part of the next upload.

[Michael Vogt (mvo)]

I think this is fixed in 0.55+cvs20041113. can you please confirm this?

[nandhp (nandhp)]

I realize that I'm a bit late, but I've never been very happy with the resolution to this bug. The fix currently in use breaks when the details expander is opened and then closed again.

The original fix made the window resizable by default with a default_width of 450. But the expander modifies the resizable parameter when its visibility is toggled. Thus, the window reverts to the original, buggy, behavior when the expander is collapsed.

I've attached a patch which instead sets a minimum size request of 426 on the progress bar, which produces a window of the same size as with the existing fix. However, this size is enforced when the expander is visible and remains effective after it is collapsed again.

Perhaps there is some reason why this isn't a good solution, but I thought I'd suggest it, since it more fully resolves the problem.