You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to use your crate unsuccessfully. When trying to get the capabilities of my screen, I get this error :
The unwrap returns thread 'main' panicked at 'called Result::unwrap() on an Err value: Failed to read capabilities string
And the detail is : An error occurred while transmitting data to the device on the I2C bus. (os error -1071241854)'
I'm on Windows, and I don't understand why it's having an error about I2C, while it's supposed to be using winapi to communicate with the screen (and the display.info.backend value indeed is"winapi").
The text was updated successfully, but these errors were encountered:
I also have this problem, For the i2C error it was from the NVIDIA-API side for me but it's not problematic in my context.
The thing I don't understand is that display.update_capabilities() is never used in ddcset-rs except for winapi but it's implemented in all ddc api. Every time I use this function I get an error saying Failed to read capabilities string.
So my final question, is why and how we should use the update_capabilities method ?
Hello,
I've been trying to use your crate unsuccessfully. When trying to get the capabilities of my screen, I get this error :
The unwrap returns
thread 'main' panicked at 'called Result::unwrap() on an Err value: Failed to read capabilities string
And the detail is :
An error occurred while transmitting data to the device on the I2C bus. (os error -1071241854)'
I'm on Windows, and I don't understand why it's having an error about I2C, while it's supposed to be using winapi to communicate with the screen (and the display.info.backend value indeed is"winapi").
The text was updated successfully, but these errors were encountered: