Raspberry Pi GPIO

Mike Doub mikedoub at gmail.com
Fri Jun 10 21:32:00 CEST 2016


Sorry,  this is beyond me as well

-= Mike 



On Jun 10, 2016, 1:15 PM, at 1:15 PM, Richard Gaskin <ambassador at fourthworld.com> wrote:
>Michael Doub wrote:
> > Richard,
> >
> > You initial gut reaction is STILL correct.   Currently the only
> > solution available to livecoders is the file method.
>
>What is "the file method"?  How do I treat GPIO connections as file 
>paths?  Somewhere in /proc?
>
>Earlier you wrote:
>
>    Look at the comments in the library it self for how to solve
>    the Accessing the GPIO (of a raspberry pi) without "sudo" problem.
>
>The stack script isn't very big, and perhaps I'm just pre-coffee but I 
>couldn't find anything there about sudo.
>
>Where should I be looking?
>
>
> > It would be wonderful if someone could write a library that allowed
> > direct access to the actual GPIO driver.  I am hoping someone with
> > LiveCode builder skills will solve this problem.  If python can do
> > it, so can livecode.
>
>I would imagine so, but in Python it's easy because someone wrote a 
>component for GPIO.  I haven't looked into this deeply so forgive my 
>ignorance, but how does GPIO present itself to an application?  A sort 
>of named pipe, or serial I/O, or....?
>
>-- 
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  ____________________________________________________________________
>  Ambassador at FourthWorld.com                http://www.FourthWorld.com
>
>
>_______________________________________________
>use-livecode mailing list
>use-livecode at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode


More information about the use-livecode mailing list