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

Parser accepts a second, undocumented angle after LRUD facing azimuth #21

Open
jedwards1211 opened this issue Feb 3, 2019 · 0 comments
Labels
quirk undocumented or unexplained behavior that may not be a bug

Comments

@jedwards1211
Copy link
Contributor

jedwards1211 commented Feb 3, 2019

The Walls Manual says that LRUDs can contain an optional 5th number that is facing azimuth. However, it also accepts a 6th number:

a	b	5	0	0	*1 2 3 4 100 200*

I'm guessing that when there are two azimuths, the first is the azimuth of the left wall distance and the second is the azimuth of the right wall distance. However a single azimuth is called a "facing direction", which I assume means the angle that the LRUD plane is facing, so a facing angle of 30 would mean left is toward 300 and right is toward 120. I haven't been able to confirm any of this.

Notes

Since adding a 7th number produces the error message "Too many LRUD distances", I can only assume this number is explicitly accepted.

The 6th number is clearly parsed as an angle because using an invalid unit like 200q produces the error message "Bad angle or azimuth qty", whereas an invalid unit on the first four numbers produces the error message "Wrong format for length qty".

While Walls allows the C flag as the 5th or 6th element (with or without a single facing direction), a C flag after two azimuths produces the "Too many LRUD distances" error again, which I assume is a bug.

@jedwards1211 jedwards1211 added the quirk undocumented or unexplained behavior that may not be a bug label Feb 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
quirk undocumented or unexplained behavior that may not be a bug
Projects
None yet
Development

No branches or pull requests

1 participant