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
It would be great (if not too complex) to add support for the RPi.GPIO pull_up_down argument of setup() since it is very common to have pull up/down set when reading an input.
I've tried the trick to output e.g. HIGH before reading but I correctly got an error saying the pin is supposed to be an input not an output.
Alternatively, I'd recommend adding the pull_up_down option anyway and just print out a warning saying it is not implemented so to ensure compatibility with existing code. A similar approach can be used for bouncetime and other optional parameters in this way the code will be fully compatible even if the functionality is not implemented.
Thanks
The text was updated successfully, but these errors were encountered:
Yes, pull-up and pull-down arguments are on the radar, but at present I'm not sure if it is fully supported by the GPIOs on the Orange Pi Zero. But I like your idea of accepting them regardless and displaying a warning.
Bouncetime should be easier to support, but in the meantime I'll also add the params and emit some warnings.
It would be great (if not too complex) to add support for the RPi.GPIO
pull_up_down
argument of setup() since it is very common to have pull up/down set when reading an input.I've tried the trick to output e.g. HIGH before reading but I correctly got an error saying the pin is supposed to be an input not an output.
Alternatively, I'd recommend adding the pull_up_down option anyway and just print out a warning saying it is not implemented so to ensure compatibility with existing code. A similar approach can be used for bouncetime and other optional parameters in this way the code will be fully compatible even if the functionality is not implemented.
Thanks
The text was updated successfully, but these errors were encountered: