forked from watabou/TownGeneratorOS
-
Notifications
You must be signed in to change notification settings - Fork 2
Debug bad walled area shape in town scene #4
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
Open
Gambitnl
wants to merge
18
commits into
master
Choose a base branch
from
cursor/debug-bad-walled-area-shape-in-town-scene-07bb
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
5a8ba53
Implement ray casting algorithm for point-in-polygon test
cursoragent 1227e0d
Refactor: Update imports, add methods, and improve type handling
cursoragent 6fb3b34
Migrate project to Vite, update build and dev scripts
cursoragent 3bf8251
Improve model generation, error handling, and polygon point-in-polygo…
cursoragent 253ee62
Refactor web app with modern UI, improved generation, and responsive …
cursoragent 1123bf5
Update August 6, 2025. 12:22AM
Gambitnl 834faa0
Update AUgust 6 2025, 12:33AM
Gambitnl cbe2127
Update August 6 2025, 12:39AM
Gambitnl aa5edee
Update August 6 2025, 01:15AM
Gambitnl 8ff4e2c
Update August 6 2025, 01:17AM
Gambitnl fee8a41
Update August 6 2025, 15:38PM
Gambitnl 236bc85
Update August 6 2025, 21:25PM
Gambitnl 916119a
Upgrade August 6 2025, 23:46PM
Gambitnl 30fdb32
Update August 7 2025, 21:16PM
Gambitnl 71f08c8
Update August 7 2025, 12:00:00 AM
Gambitnl 9aa481e
Update August 11 2025, 01:09AM
Gambitnl 2f50ec1
Update August 12 2025, 21:43PM
Gambitnl ebbe01f
Update August 12 2025, 23:34PM
Gambitnl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new implementation correctly identifies points strictly inside the polygon, which fixes the described bug. This is a great improvement!
However, there's a subtle change in behavior for points on the boundary. The previous implementation returned
truefor vertices, but the new ray-casting algorithm will returnfalsefor all points on the boundary, including vertices.This could lead to unexpected behavior if other parts of the code rely on
containsbeing true for vertices.To restore the previous behavior for vertices while keeping the new, correct check for interior points, I suggest adding the vertex check back at the beginning of the method. This is a minimal change that addresses the regression for vertices.
Note that with this change, points on an edge that are not vertices will still be considered outside. A full boundary check would be more robust but also more complex.