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

Y axis #37

Open
JollyRotter opened this issue May 6, 2016 · 3 comments · May be fixed by #38
Open

Y axis #37

JollyRotter opened this issue May 6, 2016 · 3 comments · May be fixed by #38
Assignees

Comments

@JollyRotter
Copy link

The in-game map editor's x and y axes start at the bottom left of the map, and increase in number from 1 to whatever the map's size is (so in a 50x50 map, the bottom left-most tile will be 1,1 and the top right-most tile will be 50,50). Currently the y axis in wfto-mapeditor is the wrong way round (so in the same 50x50 map, the bottom left most tile will be 1,50 and the top right-most tile will be 50,1). Below are two images to illustrate what I mean:

xyaxis01 xyaxis02

It's easier to translate a map from wfto-mapeditor to the in-game map editor if the coordinates on the x-y axes are the same, but currently only the x axis is the same. Would it be possible to flip the y axis around so it starts at the bottom of the map and counts up to the top?

@ufdada
Copy link
Owner

ufdada commented May 6, 2016

Haven't got my hands on the source code for a long time, but it seems quite possible.

ufdada added a commit that referenced this issue May 6, 2016
@ufdada ufdada linked a pull request May 6, 2016 that will close this issue
@ufdada
Copy link
Owner

ufdada commented May 6, 2016

Okay, wasn't that difficult. Would you like to test it?

https://rawgit.com/ufdada/wfto-mapeditor/Y-axis/index.html

@ufdada ufdada self-assigned this May 6, 2016
@JollyRotter
Copy link
Author

Wow, awesome! Works perfectly! Excellent work, and thank you very much!

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

Successfully merging a pull request may close this issue.

2 participants