On Wed, Jan 07, 2004 at 02:12:06PM -0400, Rob Shortt wrote: > I think this is good, but only for tiny_osd, because it can't display > over other apps (mplayer/xine/tvtime). So, if it is the osd plugin's > responsability to send the message to the running object it will also > make it better for other osd plugins that actually CAN display messages > over the running object without it knowing or caring. The tiny_xosd > plugin works like this and if you are running X then there is no need to > send the message to the running object, it may handle the display. I > am also working on a tiny_directfbosd plugin that will do the same (and > also have arbitrary graphics capabilities) for those using the directfb > output method.
Actually, it works on tvtime and mplayer (I can't confirm tvtime, but the code is there... at least I saw a commit from Mike to that effect) > Yes, I agree that it should be the osd plugin's responsability to handle > the osd/message events and only pass them along to the player/object > if neccessary, that way there's not two things trying to handle the same > event. You wouldn't want mplayer bmovl AND xosd displaying duplicate > messages. Presumably xosd would disable the mplayer one, but the rest shouldn't need to be changed. ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
