- changed title to Add support for setting non-int onevalue for capability
- edited description
Add support for setting non-int onevalue for capability
Issue #31
resolved
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)
-
reporter -
reporter - changed status to resolved
- Log in to comment