On Sun, Nov 25, 2012 at 7:29 AM, Francois Dion wrote:
> This should really be done with interrupts, but unfortunately there is
> no support in the RPi.GPIO module for that, even if you have a patched
> kernel.
Thank you for all this great information. I ended up going with a
simple solution; I c
On Sun, Nov 25, 2012 at 7:32 AM, Sean Carolan wrote:
> This is how I'm checking for a button press:
This should really be done with interrupts, but unfortunately there is
no support in the RPi.GPIO module for that, even if you have a patched
kernel.
I've done a workshop earlier this month that w
> If you show us how you check whether the button is pressed, we may be able to
> show you how to run that asynchronously.
Apologies for the previous email; I think I sent it in HTML format.
Gmail changed their user interface again...
This is how I'm checking for a button press:
modes = (weather
On 25/11/12 22:06, Sean Carolan wrote:
I'm working on a python script that runs on a Raspberry Pi. The script
detects when hardware buttons are pressed, and then runs functions based on
that input.
Oh I'm sorry, I completely misread what you wrote there. I didn't realise you
were talking about
On 25/11/12 22:06, Sean Carolan wrote:
I'm working on a python script that runs on a Raspberry Pi. The script
detects when hardware buttons are pressed, and then runs functions based on
that input.
I want to be able to always listen for a button press, no matter what the
script is doing at the
I'm working on a python script that runs on a Raspberry Pi. The script
detects when hardware buttons are pressed, and then runs functions based on
that input.
I want to be able to always listen for a button press, no matter what the
script is doing at the current moment. When a button press is d
