Software Support > DOS/WinCab
wincab Version 3.1.4 Unstable?
wwwombat:
Wow! That was a quick reply... I'd only just hit post! I'll monitor for a debug version to download and retry when ready.
Chris:
I just had a "DOH!" moment.
There are actually three message queues: the standard queue, a "timed" queue, and a retry queue. When a key is pressed, it's message is put onto the standard queue and its release message is put onto the timed queue set for a tenth of a second later. When its timer expires it moves its message to the main queue.
However, the key repeat rate can be set to 30 times per second... at maximum repeat speed, messages are being sent faster than the releases. The default repeat rate is only 5 times per second. Are you using the default rate or the maximum rate?
--Chris
wwwombat:
Checkity-checkity-check (don't remember looking at or altering that value)... so that means:-
KeyRepeatRate = 5
If it's factored into the equation, this is running on a 3.2GhZ Dual Core processor (I went nuts cause I wanted Jukebox/Mame/Pinball/Videos/PC Games, the works...)
Chris:
Well, then it's not over-repeating. And looking at the code the fail-safes are pretty fail-safe as far as preventing overflows. Still, I added code that clears any existing releases before adding a new release so even if a key is pressed thirty times in a second it will only ever have one release pending. I've also added messages to show when the delay queue fills up (there was already one on the main queue); both of these are Level 0 messages so they will show up in jbdebug.log even if the debug log is disabled.
I have not been able to reproduce the problem, but for some reason on this machine page turn animations are insanely slow which may have something to do with it.
wwwombat:
Hmmm... I just did a count of particular strings in the 2nd of my two logs.
The number of occurrences of the string
LVL1-DO_INPUT: Mouse button pressed, b = 1
is a staggering 26,931. (they appear to be in blocks of 5)
The number of occurrences of the string
LVL3-MQ_PROCESS: Processing message: -BTN_NEXTPG
is a comparatively tiny 239. Is one what I'm asking it to do versus what it has actually done?
No LVL0 messages appear at all.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version