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

Corrupt text in NewGRF settings window #5809

Closed
DorpsGek opened this issue Nov 18, 2013 · 1 comment
Closed

Corrupt text in NewGRF settings window #5809

DorpsGek opened this issue Nov 18, 2013 · 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

mart3p opened the ticket and wrote:

In the NewGRF settings window the 'Detailed NewGRF information' is not drawn correctly. Parts of the text are missing or drawn twice.

To reproduce this open the NewGRF settings window from the start screen and click on a file so that its details appear.

If the start screen is left running, random rectangular blocks of text in the information window disappear. They reappear a few seconds later.

The screenshot shows the problem.

Using Windows Vista Home Premium SP2

Attachments

Reported version: 1.3.3-RC1
Operating system: Windows

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

Rubidium closed the ticket.

Reason for closing: Fixed

In r26036

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

@DorpsGek DorpsGek added component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) bug labels Apr 7, 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