Find a way to get rid of transition functions in FlxState

[Gama11]

Really not a fan of having isTransitionNeeded() and transitionToState() in FlxState. They're only needed by the transitions classes in flixel-addons. which makes them a hack in my opinion. The system should be flexible enough that you can create addon classes like this without modifying the base FlxState class.

I'd also like to avoid them becoming part of the public API we have to keep compatibility with in a 4.0.0 release.

[Tiago-Ling]

+1

Tiago Ling Alexandre
Tel: +55 41 8819-3191

2015-12-20 8:18 GMT-02:00 Gama11 [email protected]:

Really not a fan of having isTransitionNeeded() and transitionToState()
in FlxState

flixel/flixel/FlxState.hx

Lines 132 to 149 in 637e4a5

	/**
	* Checked by FlxG.switchState to see if a transition is required before switching states
	* @return
	*/
	public function isTransitionNeeded():Bool
	{
	//override in your subclass to enable this functionality
	return false;
	}
	/**
	* Perform a visual transition, and when it's complete, call FlxG.switchState
	* @param State
	*/
	public function transitionToState(State:FlxState):Void
	{
	//override in your subclass to enable this functionality
	}

.
They're only needed by the transitions classes in flixel-addons. which
makes them a hack in my opinion. The system should be flexible enough that
you can create addon classes like this without modifying the base FlxState
class.

I'd also like to avoid them becoming part of the public API we have to
keep compatibility with in a 4.0.0 release.

—
Reply to this email directly or view it on GitHub
#1676.

[Gama11]

I think I've found a more flexible solution...

[larsiusprime]

Cool

[Gama11]

The new FlxState#switchTo() should be a bit more flexible.. Even if not, it doesn't have "transition" in the name and the implementation is simpler. :)