Hi, Currently, uvc driver and I guess all other v4l2 video drivers use internal stored control strings. This poses a problem when adding localization for this strings, since they can change between drivers. Even if driver developers are careful enough to return the same string for the correspondent control ID, a slight difference: Brightness or brightness is enough for a failed translation. Since the control ID's are defined in the V4L2 API is there any special reason why the correspondent control strings are not. I may be failing to see this correctly but at least for me it seems much logical that if all standard control IDs are already defined there, then also the name string should be made available through this central public API, making it exactly the same for all drivers.
If I'm wrong please feel free to shut me up, and kick me in the but. :-) Best regards, Paulo _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
