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

Jump to bottom

Dock construction displays "Coverage area highlight" after it has been set to off #835

Closed
DorpsGek opened this issue Jun 6, 2007 · 1 comment
Closed

Dock construction displays "Coverage area highlight" after it has been set to off #835

DorpsGek opened this issue Jun 6, 2007 · 1 comment
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Jun 6, 2007

Unaimed opened the ticket and wrote:

"Coverage area highlight" stays on after you've set it to "Off"

How to reproduce:

  1. Open the "Build ship docks" window
  2. Press the "Build ship dock" icon
  3. Set "Coverage area highlight" to "On" then "Off"

See the attached patch for the solution. diff is against r10048.

Attachments

Reported version: 0.5.2
Operating system: All

This issue was imported from FlySpray: https://bugs.openttd.org/task/835
@DorpsGek
Copy link
Member Author

DorpsGek commented Jun 8, 2007

Rubidium closed the ticket.

Reason for closing: Fixed

In r10068

This comment was imported from FlySpray: https://bugs.openttd.org/task/835

@DorpsGek DorpsGek closed this as completed Jun 8, 2007
@DorpsGek DorpsGek added component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) bug labels Apr 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DorpsGek