style cleanup: use FOREACH_ENUM( X, x ) everywhere instead of FOREACH_X( x ) for consistency

The FOREACH_X defines are not very useful, and they were created back before FOREACH_ENUM was convenient.
This commit is contained in:
Chris Danford
2007-02-23 22:29:42 +00:00
parent 808a5d2b2c
commit 0160e23705
33 changed files with 92 additions and 108 deletions
+4 -4
View File
@@ -206,7 +206,7 @@ void Course::Init()
m_bRepeat = false;
m_bShuffle = false;
m_iLives = -1;
FOREACH_Difficulty(dc)
FOREACH_ENUM( Difficulty,dc)
m_iCustomMeter[dc] = -1;
m_bSortByMeter = false;
@@ -691,7 +691,7 @@ void Course::Invalidate( const Song *pStaleSong )
// If we find a Trail that contains this song, then it's part of a
// non-fixed entry. So, regenerating the Trail will force different
// songs to be chosen.
FOREACH_StepsType( st )
FOREACH_ENUM( StepsType,st )
{
FOREACH_ShownCourseDifficulty( cd )
{
@@ -860,9 +860,9 @@ bool Course::ShowInDemonstrationAndRanking() const
void Course::CalculateRadarValues()
{
FOREACH_StepsType( st )
FOREACH_ENUM( StepsType,st )
{
FOREACH_CourseDifficulty( cd )
FOREACH_ENUM( CourseDifficulty,cd )
{
// For courses that aren't fixed, the radar values are meaningless.
// Makes non-fixed courses have unknown radar values.