At Tue, 5 Sep 2006 08:30:42 +0200 (CEST), Jaroslav Kysela wrote: > > On Mon, 4 Sep 2006, Takashi Iwai wrote: > > > Sorry, I meant to re-define every control "name" that is not > > conforming in the above. Renaming a mixer element _always_ results in > > a name mismatch _error_ in alsactl. It's handled as an error, not a > > warning. > > Note that alsactl or probably alsa-lib should be improved. We cannot > expect that names won't change and name cleanups are preferred. I would > propose to create a database with name change description to prevent these > errors and allow users switching between two ALSA driver versions more > nicely. > > The question is, if applications use these names to do something special > (if they compares them with own strings). Of course, we will break the > compatibility in this case. I would like to discuss, if adding a function > like > > int snd_mixer_compat_control_name(const char *name, > const char *alsa_version, > char *new_name, int new_name_size) > > would be sufficient to ALSA API. Hmm... How would this function be used? I still don't get it. Is it a function to be called by apps, or a function used in alsa-lib internaly? Takashi ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-devel
