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 149770 - annoying window position / size handling
annoying window position / size handling
Status: RESOLVED DUPLICATE of bug 125903
Product: totem
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2004-08-09 21:49 UTC by Markus Bertheau
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Markus Bertheau 2004-08-09 21:49:30 UTC
I use totem mainly for two things: Listening to internet radio and watching
movies. When listening to radio, I usually have the window at the minimum size,
which is what you get when you select any zoom level when there's no video. Now
when I watch a movie, I usually do it in full screen, and when the movie is
over, I quit totem with q. The next time I start totem, it starts with a window
the size of the full screen. This is very annoying and also useless for both
movies and internet radio: the movie is half off screen (because totem seems to
put the window always at (100, 50) (or so). For audio I don't need such a big
window at all. Then the maximize button, that would bring me to a state that is
good for watching movies, for example, is not on the screen. And the view menu
with the zoom entries is hard to navigate; well, because it's a menu. I should
maybe get used to the shortcuts.

I can imagine the following:

If there is no video in the media currently playing, always make the window the
minimum size.

When I start totem with a movie after quitting it in full screen mode, make it a
useful size, not full-screen-size-but-with-window-border-and-half-off-the-screen.

Thanks :)
Comment 1 John Spray 2004-08-22 00:47:31 UTC
WRT to the problem of the fullscreen window size being used on startup:
I notice that in totem_action_exit, totem_action_save_size is actually called
before totem_action_fullscreen(totem,FALSE).  However, reversing the order of
these calls had no effect: the bvw->allocation wasn't changing.  I'm not sure
what needs to be done in between in order for this to be updated to reflect the
window being un-fullscreened.  Alternatively, totem_action_save_size could just
look at the un-fullscreened size instead of bvw->allocation, but I have no idea
where in the bvw implementation this information is stored.
Comment 2 Bastien Nocera 2004-09-20 16:25:03 UTC
Mass reassign.
Comment 3 Keith Lea 2004-10-07 02:07:49 UTC
I think this is a duplicate of bug 125903.
Comment 4 Bastien Nocera 2004-10-07 11:24:17 UTC
Marking as a duplicate. Feel free to open a new bug if the problem persists
after having tried the changes.

*** This bug has been marked as a duplicate of 125903 ***
Comment 5 Markus Bertheau 2004-10-07 18:26:12 UTC
I cannot see how bug 125903 is any relevant to this. This is about starting
totem after leaving it in full screen mode.
Comment 6 Bastien Nocera 2004-10-07 22:20:52 UTC
Well, I don't understand anything in the original report. Feel free to re-open
if you feel that's wrong, but, please, explain concisely what you expect, what
you get, and how you would reproduce the problem.