Display Lists tooltip "bug"

[Phytotron]

Minor-ish thing, but the other day I accidentally hit the 'reset to defaults' in my system settings. Then, I noticed in that other recent thread Z-Man mentioned having display lists turned on. So, I looked at the relevant menu page; I had it off, and think I always have. Anyway, waited for the tooltip (that's the right term, yeah?) to come up for its explanation and recommendation (as most have), but this is what I got:

Opened up and expanded a blank text file behind these, so you could better see the cut-off at the bottom.

This is in both 0.2.8.2.1 and .2 (and as I'm sure you're aware, the two separate options for type of display list weren't in pre-0.2.8 versions). Changing resolutions made no difference, either (indeed, I had to lower it in order to get the windowed screenshot—why can't we screenshot the menus, incidentally?).

[sinewav]

Yeah, that cut-off text has bothered me forever.

[Z-Man]

Thanks. I saw this the other day, but was assuming it was due to the small window size in debug mode and ignored it. Fixed for 0.2.8.3.2 (it's non-critical, but also a risk free change.)

[Phytotron]

Are you going to fix it for the current 0.2.8.3.2? I just downloaded it again to see if you had and it's still cut-off.

In case not, and anyone watching this is wondering what they're supposed to say, I found them in english_base.txt:

Create and Call - Use displaylists; Create them and call them directly. This is the recommended way.

Create and Execute - Use displaylists; Create them let them be executed while they are filled. The expers say this is slower than Create and Call.

May want to fix "expers" while you're at it.

[Z-Man]

Are you going to fix it for the current 0.2.8.3.2?

You mean the build that's already out, date-tagged to before the report? No, a time machine is not currently in my possession. I'll be in the next beta build.

[Phytotron]

And I get flack for being a condescending smart-ass.

I admit, I didn't even notice the string of numbers at the end was a date. I usually ignore those things, assuming they're just technical geekery.

Also, "Create them [and] let them be...."

[Z-Man]

And I get flack for being a condescending smart-ass.

Heh, being condescending was not my intention. The time machine comment, that's a nerd thing. Whenever there is a problem that could be solved or an expectation that could be met with a time machine, we need to mention we don't have one or we're still working on it or ours was stolen by Edison. It's in the rule book. For the rest, you made wrong assumptions (which is totally normal from time to time) and they somehow had to get out of your brain, there is no painless way to tell you that, no way that doesn't make you feel a bit stupid for a moment. Had I wanted to be condescending, I'd have made sure to list all the reasons why it's wrong, and had my intention been to feed you a meal you're happy to dish out yourself, I'd have thrown in the one or other 'gramps' and 'preposterous' and some more words I'd have to look up first. And dammit, I wanted to do that sometime, and now I can't any more.

Also, "Create them [and] let them be...."

Oh yeah. It'll probably be a good idea to run a routine spellcheck, too. Luke did that a while back (I remember because the in this case rather silly daggy fix caused tons of merge problems), dunno whether the changes are already in the relevant branch, I'll check and merge them if they're not.