Maybe it's better OSD (tinyosd) to call the running object to display
it. I mean, if it's in Menu, ask it to display the message. If it's in
MPlayer Music Player, ask it. If in MPlayer video player, ask it, ...
With that we could have that I mentioned above and we solve the
problem that will be display the messages in Mplayer, Xine, TvTime, ...
Maybe it could be a method in the basic plugin class. So just weired
plugins (video/mplayer, video/xine, ...) override it.
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.
It seem to be more work, but it's the right way to do IMHO, since each plugin is likely to know how to display info. In that case, tinyosd should be the plugin that enqueue events and handle them. Maybe it could be renamed to event_queue. If this happens we need to define if the envent_queue calls plugins methods or plugins that ask for info. I'm for the first.
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.
-Rob
------------------------------------------------------- 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