actions/itgmania212121
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Start loading the gameplay screen as soon as the stage graphic

Browse Source 
is finished, which reduces unnecessary delay.

This also means that it's possible to have, say, an Extra stage screen with
a long, complicated graphic, without having to make every screen delay
that long before prepping.

(It's currently not possible to have different switch delays for each type; eg.
Stage 1 prepping in 1 second and switching in 3, and Extra prepping in 3
seconds and switching in 5; the switch time is constant, based on m_In.
This would be useful in the longer-complicated-extra-stage case.)
This commit is contained in:
Glenn Maynard
2003-03-17 01:48:40 +00:00
parent f1a083cee5
commit db47d0825b
1 changed files with 19 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stepmania/src/ScreenStage.cpp
+19 -6
View File
@@ -29,7 +29,7 @@
#define NEXT_SCREEN THEME->GetMetric ("ScreenStage","NextScreen")
const ScreenMessage SM_LoadPrepedScreen = (ScreenMessage)(SM_User+0);
const ScreenMessage SM_PrepScreen = (ScreenMessage)(SM_User+0);
/*
#define STAGE_TYPE THEME->GetMetricI("ScreenStage","StageType")
@@ -63,18 +63,31 @@ ScreenStage::ScreenStage()
this->AddChild( &m_Background );
m_In.Load( THEME->GetPathTo("BGAnimations","ScreenStage in") );
m_In.StartTransitioning();
this->AddChild( &m_In );
m_Out.Load( THEME->GetPathTo("BGAnimations","ScreenStage out") );
this->AddChild( &m_Out );
m_In.StartTransitioning( SM_LoadPrepedScreen );
float fStartFadingOutSeconds = m_Background.GetLengthSeconds() - m_Out.GetLengthSeconds();
this->SendScreenMessage( SM_BeginFadingOut, fStartFadingOutSeconds );
m_Back.Load( THEME->GetPathTo("BGAnimations","Common back") );
this->AddChild( &m_Back );
/* Prep the new screen once the animation is complete. This way, we
* start loading the gameplay screen as soon as possible. */
this->SendScreenMessage( SM_PrepScreen, m_Background.GetLengthSeconds() );
/* Start fading out after m_In is complete, minus the length of m_Out. This
* essentially makes m_In a timer to pad the length, so we always wait a minimum
* amount of time. It's a slightly confusing timer, though; maybe we shouldn't
* make m_Out affect it. (Maybe just make it a metric? XXX) */
float fStartFadingOutSeconds = m_In.GetLengthSeconds() - m_Out.GetLengthSeconds();
/* Never do this before we send SM_PrepScreen--we havn't loaded the screen yet. */
fStartFadingOutSeconds = max(fStartFadingOutSeconds, m_Background.GetLengthSeconds());
this->SendScreenMessage( SM_BeginFadingOut, fStartFadingOutSeconds );
//g_StageType = (StageType)STAGE_TYPE;
@@ -571,7 +584,7 @@ void ScreenStage::HandleScreenMessage( const ScreenMessage SM )
{
switch( SM )
{
case SM_LoadPrepedScreen:
case SM_PrepScreen:
SCREENMAN->PrepNewScreen( NEXT_SCREEN );
break;
case SM_BeginFadingOut: