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 received a likely defective unit of Blockstream Jade a few days ago; I'm currently in a conversation with the support team for a resolution.
The defect I observed was that the scroll wheel "double clicks" when scrolled to the right side, as in the UI element moves by 2 most of the time when I scroll to the left once. This also only happens on the right side and not the left side. Besides replacing the entire unit and replacing the scroll wheel component, I was wondering if it is possible to add a debounce time delay setting in software to mitigate this issue, since this is an otherwise perfectly functional unit, as far as I can tell. From the readme, I take it that even if I modify the code here, I'm not supposed to be flashing it onto a production device, so I'm asking if there's a good way to add this feature and whether or not it's worth the time.
The text was updated successfully, but these errors were encountered:
I received a likely defective unit of Blockstream Jade a few days ago; I'm currently in a conversation with the support team for a resolution.
The defect I observed was that the scroll wheel "double clicks" when scrolled to the right side, as in the UI element moves by 2 most of the time when I scroll to the left once. This also only happens on the right side and not the left side. Besides replacing the entire unit and replacing the scroll wheel component, I was wondering if it is possible to add a debounce time delay setting in software to mitigate this issue, since this is an otherwise perfectly functional unit, as far as I can tell. From the readme, I take it that even if I modify the code here, I'm not supposed to be flashing it onto a production device, so I'm asking if there's a good way to add this feature and whether or not it's worth the time.
The text was updated successfully, but these errors were encountered: