Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update FlxMath.hx #1522

Merged
merged 1 commit into from
Jun 10, 2015
Merged

Update FlxMath.hx #1522

merged 1 commit into from
Jun 10, 2015

Conversation

Tiago-Ling
Copy link
Contributor

The minimum value for floats in BlackBerry should be the same used for Flash, js and iOS.

This fixes problems where FlxMath.MIN_VALUE_FLOAT is used on BlackBerry (e.g. FlxG.camera.fade)

The minimum value for floats in BlackBerry should be the same used for Flash, js and iOS.

This fixes problems where FlxMath.MIN_VALUE_FLOAT is used on BlackBerry (e.g. FlxG.camera.fade)
@Gama11
Copy link
Member

Gama11 commented Jun 9, 2015

Hm... this is somewhat ridicolous, I think this has caused similar issues before on iOS, there's a good chance this will come up again on some other platform.
I don't think there's any good reason to use FlxMath.MIN_VALUE_FLOAT in FlxCamera here in the first place, another sufficiently small value should do the trick (0.000001 or whatever, that would make it more consistent with the 0.999999 value used for _fxFadeIn too).

Eventually these should probably be replaced by tweens anyway (see #1030).

Gama11 added a commit that referenced this pull request Jun 10, 2015
Using a value that small leads to floating point precision issues on some platforms like BlackBerry.
Gama11 added a commit that referenced this pull request Jun 10, 2015
@Gama11 Gama11 merged commit 8f15543 into HaxeFlixel:dev Jun 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants