From: <bar...@t-...> - 2002-07-02 18:49:49
|
hi daniel, On Fri, 28 Jun 2002, Daniel Caujolle-Bert wrote: > Humm, but i'm missing something here, who decide which configfile that > will be used ok, I think we talked about this elsewhere already (this mail thread is getting pretty long :)), I've added a parameter xine_t *xine_new (char *cfg_filename); so the ui can specify a path to a config file that will be loaded after the system-wide config file. > > xine_ao_driver_t *xine_open_audio_driver (xine_t *self, char *id, > > void *data); > > > > xine_vo_driver_t *xine_open_video_driver (xine_t *self, char *id, > > int visual, void *data); > > Okay, i also think we have to have a close_*_driver, since an UI can > xine_exit(), changing any ao/vo driver, and reinit engine. xine_exit will close all drivers, after that the ui will have to call xine_new again if it really wants to use xine again. > > void xine_init (xine_t *self, xine_ao_driver_t *ao, > > xine_vo_driver_t *vo); > > > > So, maybe, i think adding a 'char *configfilename' in this prototype > could be useful. i think this is too late as the ui will want to access the config repository already to find out which audio/video drivers to load. that's why i've added that parameter to xine_new cheers, guenter -- God may be subtle, but He isn't plain mean. -- Albert Einstein |