Merge upstream PR fixes for Haxe 4 and polygon distance#25
Closed
millionart wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This combines the currently open fixes from:
Polygon.get_square, Ward density inference, and conservative Lime/OpenFL version pinsPolygon.distanceso it returns the minimum distance across all vertices instead of the first vertex distanceNotes
The dependency versions from #16 are not current as of 2026, but they are the conservative versions proposed by the existing PR and are lower-risk than jumping this old project directly to the latest Lime/OpenFL releases without a dedicated migration pass.
Validation
git diff --checkgit diff --check origin/master...HEADHaxe/OpenFL build validation was not run because this local environment does not have
haxe,haxelib, orlimeinstalled.