should resize when playing audio

[David Prieto]

Binary package hint: totem

Totem automatically resizes when you open a video, but it does not when you play an audio. If you do so you get a big window (same size as the last video you played) but then if you press 1 it gets much smaller.

Is there a good reason for us to have a huge window at start, and not have it resized automatically and right away?

[Pascal De Vuyst (pascal-devuyst)]

Which version of Ubuntu or totem are you using?
I don't see this problem in Ubuntu Edgy on my PC, totem resizes as expected (size 1:1) after opening an audio file.

[David Prieto (frandavid100-gmail)]

I'm using Totem 2.17.91, on Ubuntu Feisty.

But I can't recall Totem ever resizing audio files... not in Edgy, not in Dapper, not in Breezy.

[Sebastien Bacher (seb128)]

totem adjusts the window size to the video when playing one, there is no such parameter for an audio file, why would totem change the window dimensions from the one you used previous which are likely the one you want to use?

[David Prieto (frandavid100-gmail)]

"there is no such parameter for an audio file"

And yet, the size is adjusted when you press 1.

"why would totem change the window dimensions from the one you used previous which are likely the one you want to use?"

You got a point there, but why would you want a big window if you're just playing audio? It serves no purpose and just gets in the way, IMO.

[Sebastien Bacher (seb128)]

> why would you want a big window if you're just playing audio

for the video effects displayed while playing (that's a preferences option)

[David Prieto (frandavid100-gmail)]

Yep, you are totally right there.

Would it be possible to auto-resize only if the video effects are disabled?

If not, well, at least I tried :)

[Sebastien Bacher (seb128)]

Making the windows autoresized doesn't make better sense than using the previous dimension, some people probably set the window size and position to something that fits their use, there is no reason to break that for them. I'm closing the request, feel free to open a bug upstream about it if you want to argue, they are the right people to speak about such changes since we are not likely to want to make a distribution specific behaviour for that