Timeline for Converting from RPi.GPIO to circuit python digitalio
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18, 2020 at 2:14 | vote | accept | alforddm | ||
| Aug 16, 2020 at 9:20 | answer | added | Ingo | timeline score: 1 | |
| Aug 15, 2020 at 9:41 | comment | added | Ingo | Please create an answer about the solution to your question and accept it after two days with a click on the tick on its left side. There is nothing wrong with self-answering. Only accepting an answer will finish the question and it will not pop up again year for year. | |
| Aug 9, 2020 at 23:33 | comment | added | alforddm | Thank you, that is exactly what I needed to know. | |
| Aug 9, 2020 at 23:25 | comment | added | Dougie | You would be better supported that way. | |
| Aug 9, 2020 at 23:19 | comment | added | alforddm | So, I would be better off continuing to use the RPi.GPIO interface for the kiln element pins for the sake of future compatibility/more elegant code even though I'm importing two input/output interfaces? Sorry if these are basic questions, I'm self taught and couldn't find these particular questions addressed anywhere in my searches. | |
| Aug 9, 2020 at 22:51 | review | Close votes | |||
| Aug 24, 2020 at 3:01 | |||||
| Aug 9, 2020 at 21:41 | comment | added | Dougie | RPi.GPIO is better supported and as it's part of RaspiOS should always work on any current or future version of the RPi. | |
| Aug 9, 2020 at 21:24 | history | edited | alforddm | CC BY-SA 4.0 |
edited title
|
| Aug 9, 2020 at 21:07 | review | First posts | |||
| Aug 9, 2020 at 21:41 | |||||
| Aug 9, 2020 at 21:06 | history | asked | alforddm | CC BY-SA 4.0 |