VOGONS

Search

Common searches

Num Lock and num-pad comma bugs

Topic actions

First post, by petob

Posted on 
User metadata
Rank Newbie
Rank
Newbie

On 28.9.2004 I tried latest CVS builds (from the net and my own build) on several different PCs with Windows XP Pro and I have found these bugs:
1) Right after DOSBox start Num Lock status is not read, because even when it is on, it is functioning like when it is off - num-pad numbers are doing navigation. Functionality is right only after switching Num Lock off and on.
2) Num-pad comma "." key is not functioning no matter Num Lock is switched on or off.

Reply 1 of 2, by Qbix

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

the . bug has been fixed.
you could get it by pressing shift 😉

the numlock thingie isn't easy to fix. as you can't ask sdl for the current state.

and our mapper doesn't check the mods all the time on a keypress.

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 2, by petob

Posted on 
User metadata
Rank Newbie
Rank
Newbie

> the numlock thingie isn't easy to fix. as you can't ask sdl for the current state and our mapper doesn't check the mods all the time on a keypress.

okey, but you can set the state of numlock, dont you? so set the numlock to f.g. "off" on every start of dosbox and it will work 😉

MS Windows XP Pro US SP1 on AMD Athlon 2500, Asus A7N8X deluxe, 512MB dual channel DDR 400MHz, serial ATA RAID with 2x Seagate Barracuda 7200.7 120GB, ATI Radeon 7500 AIW 32 MB

Go to top of page Go to top of page
Back to DOSBox Development
Close window
Close window