Closed GoogleCodeExporter closed 8 years ago
1. Not possible to do properly with gnome-mplayer at the moment due to the way
the
video window is drawn
2. This option is already in the code
Original comment by kdeko...@gmail.com
on 19 Oct 2009 at 12:54
sorry, but about the second suggest, i still only can make gnome-mplayer window
always ontop no matter it is playing or not. i mean i wan't it ontop only when
it is
playing and when stoped or plused, it can be covered by other windows.
Original comment by jarry...@gmail.com
on 20 Oct 2009 at 2:11
I'll have to think about that as it adds extra complexity to that functionality
and
yet another option.
Original comment by kdeko...@gmail.com
on 20 Oct 2009 at 12:48
plus: maybe the window should not be always ontop when playing music, either.
Original comment by jarry...@gmail.com
on 22 Oct 2009 at 7:00
just an idea for jarryson's first suggestion but maybe looking at smplayer's
code
would help in achieving that no? Smplayer has managed to do exactly what he
describes. And it works on my computer! :)
Original comment by menino.f...@gmail.com
on 5 Mar 2010 at 11:50
I really don't look at the SMPlayer code at all. I do my thing and they do
theirs.
I'm guessing they are using some QT feature that allows them to composite the
controls on to the screen.
Original comment by kdeko...@gmail.com
on 6 Mar 2010 at 1:42
no, i mean like totem do, draw another control bar when full screen. do not
scale
the video
Original comment by jarry...@gmail.com
on 6 Mar 2010 at 4:46
Jarryson you read in my mind: also for me the full screen control bar is really
an
important thing to consider to improve gnome-mplayer. The video blink is very
very
annoying.
If I could take one thing from SMPlayer would be this. Then, as jarryson said,
you
developers could see into the Totem code.
Original comment by rez...@gmail.com
on 22 Mar 2010 at 11:35
SVN has an implementation of the control bar on top of the video.
Original comment by kdeko...@gmail.com
on 4 May 2010 at 4:19
Original comment by kdeko...@gmail.com
on 8 Jul 2010 at 2:12
Original issue reported on code.google.com by
jarry...@gmail.com
on 19 Oct 2009 at 12:01