On Tue, Dec 14, 2010 at 7:05 AM, Greg Ward <[email protected]> wrote: > Hi all --
Hello Greg. I've made the same improvement for Windows output plugin. I have to say that it suffers from the same broken API. It's designed for displaying things in graphical UI, but not for writing simple configuration files. Currently Windows output plugin supports either device id (magic non-negative int) or user friendly name (both are very uneasy to find out). Configuration option is the same for both cases. It's called "device". It's easy to distinguish what are actually specified by user so name collisions practically shouldn't happen. I think you should use the same approach for consistency. Afaik all output plugins that support device selection use exactly that name. There is one more problem -- no easy way to find out device id. One of the possible solutions I was thinking of is adding a special "enumerate" method to output plugin. As the name says it will enumerate all possible devices (if supported by underlying API) and print them somehow. It should be invoked when mpd is started with special parameters (like "mpd enum output_plugin_name" or "mpd enum" for default output plugin). However this was neither implemented nor discussed. The second solution is making a simple program that just prints avaliable devices along with all nessesary information like device ids. I've made such program for windows output, but it isn't published anywhere except this mailing list. -- Denis ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Musicpd-dev-team mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
