Skip to content

Correct behavior of KEYER_MODE_ULTIMATIC and KEYER_MODE_ULTIMATIC_ALTERNATE. #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xchrishawk merged 1 commit into from
Aug 25, 2025
Merged

Correct behavior of KEYER_MODE_ULTIMATIC and KEYER_MODE_ULTIMATIC_ALTERNATE. #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/main/application/keyer.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -429,6 +429,10 @@ static state_t get_next_state( void )
return( STATE_INTERLEAVED );

case KEYER_MODE_ULTIMATIC:
// The first activated paddle wins
return( s_state );

case KEYER_MODE_ULTIMATIC_ALTERNATE:
// The most recently activated paddle wins
if( is_bit_set( inputs, INPUT_TYPE_PADDLE_LEFT ) &&
is_bit_clear( prev_inputs, INPUT_TYPE_PADDLE_LEFT ) )
Expand All @@ -448,10 +452,6 @@ static state_t get_next_state( void )
return( s_state );
}

case KEYER_MODE_ULTIMATIC_ALTERNATE:
// The first activated paddle wins
return( s_state );

default:
// This should not be possible
fail();
Expand Down