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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider improving PathFinder UX #678

Open
davesmith00000 opened this issue Jan 6, 2024 · 0 comments
Open

Consider improving PathFinder UX #678

davesmith00000 opened this issue Jan 6, 2024 · 0 comments

Comments

@davesmith00000
Copy link
Member

@mprevel has done a fantastic job producing a new path finder for Indigo, I've integrated it into a project and it works perfectly. 馃挭

I would however like to work on the UX a bit, not immediately, happy to let it stew for a while and see how it feels after I've been using it for a bit. Maybe this then goes into a future release along with the SearchGrid deprecation.

On PathFinder, I like a small extra method added called nextMove, which just runs findPath and gives you the next move, if there is one, i.e.:

def nextMove(start, end, pathBuilder): Option[Point]
def nextMove(start, end, pathBuilder, default: => Point): Option[Point]

Are there any other functions like that, that someone might want?

With PathBuilder I don't have many concrete asks yet, but I'd like the options to be more discover-able / configurable. Maybe it's something like (I'm making this up!):

PathBuilder
  .fromRectangle(room)
  .noDiagonals
  .withImpassible(impassible)

Also is PathBuilder really a path builder? Or is it some sort of map/grid builder? Just musing. 馃

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

No branches or pull requests

1 participant