Official Game Feedback
-
> mniip told me it was fixed
He lied, it's still broken T__T
> what's broken about numpad?
Numpad keys act as if NumLock was on and off at the same time. Pressing Num7 acts as if both 7 and Home were pressed at the same time, Num8 - both 8 and UpArrow etc...
-
@arK (View Post)
does that happen when numlock is on or off?
Also how does the numpad act in the current version? -
> does that happen when numlock is on or off?
When it's on. If it's off TPT ignores Num[0-9].
> Also how does the numpad act in the current version?
NumX := Num[0-9]
NumLock on: NumX => X, Shift+NumX => nothing
NumLock off: NumX => nothing, Shift+NumX => nothing
BTW: socket.gettime() has awful precision, +/-[3-10] FPS at 60+ - click
Edited once by arK. Last: 9th Mar 2014 -
@arK (View Post)
I'm not sure if the numpad can be fixed, but maybe if it's redone in a different way it will work somehow, idk. It works for mniip though, there must be something different about your numpad.
Also for socket.gettime(), you have to measure the average fps over multiple frames, you can't just directly try and get the fps every single frame. -
> I'm not sure if the numpad can be fixed
Well, in the mean time it would be nice to undo this.
> you have to measure the average fps over multiple frames
I knew you'd say that. Anyway, this is even more wasteful... TPT already did that.
> you can't just directly try and get the fps every single frame.
Why not? PerformanceCounter (aka Multimedia Timer, aka HPET) has microsecond resolution, it's is more than enough to count FPS with 2 decimal places without averaging.
EDIT: huh, actually, I guess averaging is somewhat required. Since this is kinda "momentary FPS". Nah, nevermind...
Edited once by arK. Last: 9th Mar 2014 -
@arK (View Post)
There's socket.gettime() with millisecond precision.
Multimedia Timer is a windows thing.
Btw. I just did some extended numpad testing. Still cannot reproduce your issueEdited once by mniip. Last: 9th Mar 2014 -
> There's socket.gettime() with millisecond precision.
Not sure about that. I'm too lazy to test it myself, guy on lua-users says: (at least on windows) socket.gettime has a resolution of 64 ticks/second (which is not that great)
> Multimedia Timer is a windows thing.
AFAIK HPET (and a bunch of other high res. counters) is avaliable on linux via clock_gettime
Edited once by arK. Last: 9th Mar 2014 -
@arK (View Post)
I know about clock_gettime, in fact, I was the one to use it in TPT, but you were talking of Multimedia timers. -
Yeah, saw your commit with clock_gettime. Multimedia Timer == HPET.
Anyway. NumPad still doesn't work properly. Didn't fix it.
In fact, now it's even funnier: 1, 2, 4, 6, 7, 8 act like End, Down, Left, Right, Home, Up respectively. 5 = 5. 3 = 3 and 9 = 9, I'm not entirely sure about that though, PgUp and PgDn have no function in text boxes.
-
@arK (View Post)
Those keys are supposed to do just what you said when num lock is off, and with num lock on should all be the number keys. If you aren't getting this behavior, it's just your keyboard, because from what I can tell about SDL, everything looks right.
It's better than it doing two things at once, that's all I fixed.
Maybe the only thing that could be fixed is 3, 5, and 9 getting through with num lock off, but it's not that big of a deal.
