Currently, the default drivers are implemented by simply registering the respective drivers an extra time, using the name "default". The problem with that is that there's no direct indication of which drivers are actually used as defaults. For examyple, 'a2play -d?' can only present the defaults as '"default" (\<TYPE>)', which isn't of much use at all.
Currently, the default drivers are implemented by simply registering the respective drivers an extra time, using the name "default". The problem with that is that there's no direct indication of which drivers are actually used as defaults. For examyple, 'a2play -d?' can only present the defaults as '"default" (\<TYPE>)', which isn't of much use at all.
There must be a better way of handling this...