Quote:
Originally Posted by kovidgoyal
I think what kiwidude is asking for is a centrally maintained cache of seen uuid-name mappings that are automatically updated by the device subsystem on connect of a device.
|
Yea, I know. However, having that cache will also require a) having the infrastructure to rename devices and cards, which leads immediately to b) changes to use that name wherever the device __class__.__name__ is used now. Then there would be the follow-on requests. For example, I am absolutely certain that within minutes of releasing such a thing, there will be requests to change plugboards to use the new device name instead of the current class name. Then after changing it to use device names, there will be complaints that the old way (generic class names) no longer works. Then when both are supported, there will be complaints that the two forms aren't kept in sync. There will be requests to make save templates device-name specific. And on and on. This isn't a hassle I am interested in taking on. I will leave it to the people who want to use this stuff.