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

Catch up with upstream. #16

Merged
merged 429 commits into from
Apr 21, 2016
Merged

Catch up with upstream. #16

merged 429 commits into from
Apr 21, 2016

Conversation

IBwWG
Copy link
Collaborator

@IBwWG IBwWG commented Apr 21, 2016

No description provided.

Gama11 and others added 30 commits February 7, 2016 17:15
- only apply it when necessary
- code cleanup
- threw out the old "we center it ourselves so it doesn't blur to hell"-workaround - doesn't seem necessary anymore
It causes issues with the positioning of outlines / shadows. Also, the inserted spaces can be quite noticable...
The terms are used pretty interchangeably, but let's be consistent with what the GitHub description says.

[skip ci]
Makes sense in a way, since it's only used for the Readme on GitHub.. Less clutter in the root directory.
[skip ci]
The text position is slightly different on Flash and Native, so hardcoding the pixel x / y was problematic.
Default true so as to not break existing code.
Has some issues with assets being included.
This is a better fix for the old blurry lines bug on flash.
Beeblerox and others added 29 commits April 9, 2016 18:51
- the import warnings only appear with checkstyle dev because of some fixed crashes
- workaround for crash in FlxGame#updateInput() (see HaxeCheckstyle/haxe-checkstyle#238)
- added TestSuite to excludes again
Seems like TextField#length was implemented only recently on legacy.
Closes #1819
* The top and left edges of checked objects were not registering as overlapping, when they should be.  (Consider the example of a single pixel at 0,0: the former could would never register an overlap with the mouse, always looking for your position to be > 0 and < 1.  Even though it's a float, it still gets updated to integer values when you move the mouse.)

May seem trivial, but when you have a button at the edge of a full-screen game, it becomes important.

* Fix test by moving button out from under the cursor.

* Add unit test for #1818.  Also make the existing unit test remove from the state afterwards so we don't double-add, while leaving the existing tests independent of having been add()ed.
- fixed graph line starting from upper left / (0, 0)
- fixed graph being drawn on top of x axis (one pixel above now)
- fixed x axis not showing on native targets
Also don't build FlxNape on cpp to reduce build times and avoid termination.
@IBwWG IBwWG merged commit a197f5c into codingthat:dev Apr 21, 2016
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.