SH↓s has unexpected behavior in triggering CFs. Defect?

GoogleCodeExporter commented 8 years ago

Which board (stock / gruvin9x / sky9x / Taranis) are you using?
Taranis
What is your openTx FW version?
2834
What is your openTx EEPROM version?
Don't know 
What steps will reproduce the problem?
1.Using SH↓s twice for CFs.
2.Using SH↓l before SH↓s.

3.

What is the expected output? What do you see instead?
If I use SH↓s for 2 or more CFs, I expect all to 'fire' in sequence  when I 
do SH↓s. Only the first one happens. Tested using Play Track - only first CF 
happens. 

Also (related?), if I configure  SH↓l for CF10 and SH↓s CF11, CF11 never 
'fires'.

Please provide any additional information below.

I'm asking whether this is a defect. I'd also like to suggest that it would 
useful to have SH↓s and SH↓l available for use in configuring Custom 
Switches.

Original issue reported on code.google.com by bur...@gmail.com on 1 Dec 2013 at 3:58

GoogleCodeExporter commented 8 years ago

Issue 190 has been merged into this issue.

Original comment by bernet.a...@gmail.com on 2 Dec 2013 at 6:37

GoogleCodeExporter commented 8 years ago

Fixed on SVN. Will be in next minor release

Original comment by bson...@gmail.com on 30 Dec 2013 at 8:16

Changed state: Fixed

Newcal / opentx

SH↓s has unexpected behavior in triggering CFs. Defect? #191