On Sun, Jun 28, 2009 at 3:58 PM, Adam Charrett<a...@dvbstreamer.org> wrote: > On Sat, 2009-06-27 at 09:08 -0500, Evan Hisey wrote: >> On Sat, Jun 27, 2009 at 3:54 AM, Adam Charrett<a...@dvbstreamer.org> wrote: >> > On Fri, 2009-06-26 at 17:51 +0200, Duncan Webb wrote: >> >> Adam Charrett wrote: >> >> > On Thu, June 25, 2009 4:52 pm, Duncan Webb wrote: >> >> >> Author: duncan >> >> >> Date: Thu Jun 25 11:52:25 2009 >> >> >> New Revision: 11605 >> >> >> >> >> >> Log: >> >> >> Removed dialog.x11_overlay_display being activated by default, seems >> >> >> to be >> >> >> causing problems with the users >> >> > >> >> > Duncan, I disagree with this, the simpler option in the short term is >> >> > for >> >> > the users not to install kaa.display. Currently only the >> >> > dialog.x11_overlay_display uses kaa.display in freevo 1 so it not a >> >> > problem. >> >> >> >> >> >> The trouble with the x11_overlay_display plug-in is that people lose >> >> information, such as the selected audio, selected subtitle track and >> >> playback speed. This is not really good as a default. >> >> >> > >> > Which is fair enough then remove it from the branch not the trunk, where >> > main development should be taking place and the issues can be fixed, you >> > would expect trunk to be unstable but have the latest features. >> > >> >> Having it default disabled, till it is a least got most of the >> features of the OSDs it is replacing sounds like a good idea. If >> people want to play with it then they can enabled it like anything >> else. It is still in the trunk, it still can be tested and developed >> just won''t catch people by suprise this way. > > That's the problem it won't get tested! I can see its a good idea to be > disabled on the branch, but it does need more testing which is why it > would be good to be enabled by default on trunk.
I have to agree that it needs testing and by and large anything not enabled by default doesn't get as well tested. The main problem I was having with it is a focus problem which I have just solved with mplayer's -fstype option set to none. I was wondering btw if this is in the last released tar ball that mplayer used before going on the stance that svn is great and the one most distros still use. If so the code in freevo to enable fullscreen should be modified to include a fstype, otherwise it won't allow anything over it(such as the osd). I used '-fstype none' in my local_conf.py. Thanks Jonathan > The contention issue is the mplayer/xine time/position OSD where I > disabled the underlying players OSD, I think the best thing to do here > is add a variable to each player to allow the new OSD to be enabled, > kind of going against my own complaint above, but it does mean that > other OSDs will still get displayed when the players are running. > > Cheers > > Adam > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Freevo-devel mailing list > Freevo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freevo-devel > -- ASUS m3a78 mothorboard AMD Athlon64 X2 Dual Core Processor 6000+ 3.1Ghz 4 Gigabytes of memory Gigabyte NVidia 9400gt Graphics adapter Kworld ATSC 110 TV Capture Card Kworld ATSC 115 TV Capture Card ------------------------------------------------------------------------------ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
