Re: button command mixt up
Hi,
You wrote :
IF button NOT pressed Opmode = opmode +1 ( using goto Button_pressed )
IF button pressed Opmode = opmode +1 ( NOT jumping )
so, it's quite a normal behaviour ... :rolleyes:
just TRY
Code:
B0 = 0
BUTTON Next1,1,100,10,B0,1,Button_pressed
GOTO Button_not_pressed
Button_pressed: 'if Next1=1 then Op_Mode = Op_Mode + 1
Op_Mode = Op_Mode + 1
if Op_Mode > 1 then Op_Mode = 0
Button_not-pressed:
Goto GetModeOfOperation
It's not written in the smartest way (!) ... but will help you to understand what's going on. It also effectively uses the debounce tempo ... ( if condition is NOT true, there's NO debounce time ( obvious, but not told in the manual ...)
remember B0 has to be ( most of time ) reset just before BUTTON command ...
BTW ... using the auto-repeat mode just to toggle the " mode " value looks a bit overkill ( dangerous ? )... as you already are in a loop ... :D
Alain
Re: button command mixt up
Hi,
I tried you code, not much difference except for the extra empty function Button_not-pressed:
I tried these four config, but every time the menu cycles constanly between the options...
BUTTON Next1,1,100,10,B0,1,Button_pressed
BUTTON Next1,1,100,10,B0,0,Button_pressed
BUTTON Next1,0,100,10,B0,1,Button_pressed
BUTTON Next1,0,100,10,B0,0,Button_pressed