Glenn Maynard 55efe79054 Most of the time we use a GameCommand to store state, we don't want ...

Apply() itself to load the screen; we want to stuff it in m_sNextScreen
and let the normal screen loading code path do it.  That's why we have
GetAndClearScreen.

However, GetAndClearScreen is a non-const, and applying a GameCommand
should be a const operation.  It doesn't get along well with screen
reuse; once you've applied it, you've destroyed the GameCommand.

Instead, hold a flag indicating whether or not to apply screens, and
set this true on load when we handle it manually.  We should probably
*always* do this, and never load a screen within GameCommand itself, so
this may go away soon (always on).

2006-01-15 08:00:37 +00:00

stepmania

Most of the time we use a GameCommand to store state, we don't want

2006-01-15 08:00:37 +00:00

S

Description

Mirror of https://github.com/actions/itgmania212121

554 MiB

Languages

C++ 85.7%

Lua 4.3%

C 4.3%

Rich Text Format 2.3%

CMake 1.1%

Other 2%