Doesn't post#2 with the use of Select Case do what you want with the least code/var usage?
Ioannis
|
Re: My code for ADC button handling, it works, but can it be slimmed down?
Doesn't post#2 with the use of Select Case do what you want with the least code/var usage?
Ioannis
|
Re: My code for ADC button handling, it works, but can it be slimmed down?
No it does not.
It does not do "do not repeat action until user releases and pushes key again"
|
Re: My code for ADC button handling, it works, but can it be slimmed down?
Something like that then?Code:if !flag then adcin 1, adcval 'read keys SELECT CASE adcval CASE < 10 : left=left+1:flag=1 'detect button presses CASE < 100 @ NOP CASE < 130 : right=right+1 :flag=1'detect button presses END SELECT endif
Ioannis
Last edited by Ioannis; - 7th January 2022 at 20:40.
|
Re: My code for ADC button handling, it works, but can it be slimmed down?
Yes and we again will have extra "left" and "right" variables, one per each button - what I wanted to avoid
|
Re: My code for ADC button handling, it works, but can it be slimmed down?
maybe I am a bit slow.. But how you can have 40 buttons but not 40 variables to distinct between them?
Ioannis
|
Re: My code for ADC button handling, it works, but can it be slimmed down?
ADCIN X,ADVAL
IF ADVAL=20 then Gosub Y1
IF ADVAL=10 then GOSUB Y2
IF ADVAL=30 then GOSUB Y3
and so on.
|
Re: My code for ADC button handling, it works, but can it be slimmed down?
So at any given moment you will not know which button was hit and will have to scan again.
But even so, a flag for each button pressed is needed to keep it from regarding it as new press.
Ioannis
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks