Add support for setting non-int onevalue for capability

Issue #31 resolved
Eugene Wang repo owner created an issue

Allow setting one-value to capability object with complex values like string or frames. This will pave way for working with caps that uses these non-int values.

Note: reading non-int one values already works, just need to support write part.

Comments (2)

  1. Log in to comment