This isn't reachable; we'll always exit through the bEndThisScreen path.
Actually, this changed behavior a little, if a screen was in NAV_THREE_KEY_MENU and used SELECT_MULTIPLE rows. That combination doesn't make much sense, though; you'd have to press start on MULTIPLE rows and right on SELECT_ONE rows. That NAV mode is meant for SELECT_NONE.
This commit is contained in:
@@ -953,9 +953,7 @@ void ScreenOptions::ProcessMenuStart( const InputEventPlus &input )
|
|||||||
ChangeValueInRowRelative( m_iCurrentRow[pn], pn, 0, input.type != IET_FIRST_PRESS );
|
ChangeValueInRowRelative( m_iCurrentRow[pn], pn, 0, input.type != IET_FIRST_PRESS );
|
||||||
break;
|
break;
|
||||||
case NAV_THREE_KEY_MENU:
|
case NAV_THREE_KEY_MENU:
|
||||||
/* Don't accept START to go to the next screen if we're still transitioning in. */
|
ASSERT(0); // unreachable
|
||||||
if( input.type == IET_FIRST_PRESS && !IsTransitioning() )
|
|
||||||
this->BeginFadingOut();
|
|
||||||
break;
|
break;
|
||||||
case NAV_FIVE_KEY:
|
case NAV_FIVE_KEY:
|
||||||
/* Jump to the exit row. (If everyone's already on the exit row, then
|
/* Jump to the exit row. (If everyone's already on the exit row, then
|
||||||
|
|||||||
Reference in New Issue
Block a user