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

Not reading obstacles properly and passing through them #5

Open
GoogleCodeExporter opened this issue Jan 27, 2016 · 3 comments
Open

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Inserting a map where 0 is possible paths and 1 is an obstacle
2. A huge obstacle is in the middle of the map, a solid obstacle 
3. Path generation will still result in entering the obstacle area
4. Clearer example is in the excel sheet

What is the expected output? What do you see instead?
1. Nodes generated supposed to go around the map however nodes that are 
generated go through the map

What version of the product are you using? On what operating system?
1. Pathfinder.1.3.as on Windows7 using FlashBuilder

Please provide any additional information below.
1. Attached is the map file in excel for your reference.
2. The goal is to use diagonal traversing.

3. Only amendment made is
        public function loadMap(m: Array) {
            map = m;
            tmpMap = new Array();   
            dimensionX = map.length; 
            dimensionY = map[0].length;
        }

4. m passed in is a 2d array generated as such
    i.e 
    var map:Array = new Array();
    var map2:Array = new Array();
    map2.push(0); ...... map2.push(1);...... map2.push(0);
    map.push(map2); .... map.push(map2);

5. The result of the map generated is in the file attached

Original issue reported on code.google.com by nutcas...@gmail.com on 11 May 2012 at 5:39

@GoogleCodeExporter
Copy link
Author

[deleted comment]

1 similar comment
@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

My mistake, i figured it was (x,y) or (col,row) but rather it was (y,x) or 
(row,col). Didnt see anywhere that stated it was row then col although 
technically most people follow row-col where as i was still thinking of x,y. 
Could be useful to state this somewhere in the wiki or the code as a comment.

Original comment by nutcas...@gmail.com on 11 May 2012 at 9:06

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant