thoughts on numeric grids about easystarjs HOT 5 CLOSED

Hey kkoch. Thanks for the issue.

Do you think your problem could be solved with only one new method setAcceptableThreshold ?

Why might an explicit setWeightedGrid function be necessary ?

from easystarjs.

The purpose of setWeightedGrid would be to assign costs to each tile based on its value. If i ran something like this:

var easystar = new EasyStar.js();
easystar.setGrid(this.map);
easystar.setAcceptableTiles([true]);
easystar.enableDiagonals();

Even if the values in map are numeric it wouldnt call easystar.setTileCost(tileType, multiplicativeCost); for each number in there would it? My thought is having a setWeightedGrid function that assigns the cost to each tile according to its number and maybe flag it as a weighted cell so it could react to changes in the values.

I havent really looked into the source too much yet so I'm not sure exactly what would have to be done to accomplish this.

from easystarjs.

Thinking about it more, it wouldnt have to actually set the tile cost but maybe flag it as numerically weighted and when we look at the tile to get the cost we could just return the value

from easystarjs.

I understand now. You want to use setWeightedGrid as a way to batch-set tile costs, or even possibly create a second data structure to store these weighted values separately from the associated values from setGrid.

After thinking about it some more, I think this use case is pretty specific to your own needs. Something like this makes more sense to me as functionality that sits compositionally outside of EasyStar itself. You could keep track of these impassable tiles separately in your own code, and make them impassable with EasyStar by using the API calls setAcceptableTiles() or avoidAdditionalPoint().

from easystarjs.

no problem, thanks!

from easystarjs.