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

FIX: Text display on windows with larger font sizes #182

Open
rkmaddox opened this issue Aug 18, 2014 · 3 comments
Open

FIX: Text display on windows with larger font sizes #182

rkmaddox opened this issue Aug 18, 2014 · 3 comments
Labels

Comments

@rkmaddox
Copy link
Contributor

So the recent addition of font control in screen_prompt has revealed what I anticipate to be a nasty Pyglet bug. Displayed text has random (as far as I can tell) but reproducible spacing issues where large amounts of horizontal space are placed in between letters in the string. This is happening post-wrap, as it causes the text to go off the screen to the right instead of creating more lines.

Problem gets worse with increasing text size (wanted to use 40). Workaround was to use a smaller text size (seems to be OK with 30). This will need to be fixed, as some subjects have expressed difficulty reading instructions at the default size of 24 pts.

@rkmaddox rkmaddox added the bug label Aug 18, 2014
@larsoner
Copy link
Member

Awesome! Argh... yeah probably no easy fix for this. Might actually be easiest to calculate the wraps ourselves and insert the newlines. Plus then we can detect if the line is too long horizontally or vertically, and produce a warning or error. The logic shouldn't actually need to be too many lines if we make some reasonable-ish assumptions about the font.

@rkmaddox
Copy link
Contributor Author

Problem doesn't seem to be with the wrapping, though, since the wrapping is unaffected. It's just that in Windows, these random spaces (but likely not actual space or tab characters) are added. Seems to be a rendering issue?

@larsoner
Copy link
Member

I bring up wrapping because I expect the problem to go away with wrap=False, does it not?

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

No branches or pull requests

2 participants