Introduced in commit "Add togglemenu command" bf2b04.
Don't let UI key event changing key catcher affect bind parsing. Bind parsing itself will never change the key catcher.
Example of issue: if mouse1 is bound to +attack when clicking Resume Game, player will shoot until releasing the mouse button.
Mouse button should have to be released and pressed again before player will shoot.
* differing screen resolutions and network settings are now honoured when changing fs_game
* Fix hunk memory leak on game_restart
* Move cls.state and cls.servername to clc so connection state is fully preserved over game_restart
* Revert back to previous fs_game after disconnecting from a server that triggered a game_restart
* Fix error dialog popping up after every game_restart if an error happened previously (reported by Ensiform)
- Fixed that not all commands added by CL_Init() would be removed by CL_Shutdown()
* Fixed some whacky indentation in q_shared.c
* Allow single character keys e.g. 'c' to be used in cl_consoleKeys in addition
to ASCII characters
* Experimental code to ignore dead keys
ignoring completely' from r1459; it can't ever work acceptably, especially on
azerty/qwertz layouts
* Make the ordering of the output from in_keyboardDebug more sensible
* Add cl_consoleKeys cvar, a space delimited list of key names or characters
that toggle the console
autocompleting -- you're still all WRONG :p
* Fix bugette where the completee didn't get its case copied from
the completed token
* Add functionality to autocomplete key names
* Don't build client command completion on the dedicated server
* (bug 2946) Console scrolling broken (identified by misantropia)
+ Field_VariableSizeDraw contained a hack to ensure the cursor was always
visible. Unfortunately this interfered with scrolling long lines. Move the
hack to a different place
+ Removed commented code in the same function
+ Reworked Field_KeyDownEvent to use a switch( ... ) and set edit->scroll in
every case, thereby avoiding scrolling issues when "Home" or "End" are
pressed
at 256 for mod compatability reasons. ioq3-only mods may
chose to use MAX_KEYS for checking binds in order to get full
key support, but at the cost of breaking compatability with
older clients.
* (bug 2741) remove some lingering 256-key hardcoding
* properly check bounds of keynum in Key_IsDown(), Key_SetBinding(),
and Key_GetBinding()
keycatchers in a bad place since they see a key press for a key that is
already in a down state. Simply clearing the down state of all keys as
the console is toggled seems like a simple fix.
- No longer does weird stuff like move the cursor inappropriately
- Autocomplete works with compound commands
- Special autocomplete on some commands e.g. \map, \demo
- Removed various hacks used to counter the original autocomplete code
* Updated TODO
* Moved ChangeLog to root
* Updated ChangeLog
* s/Foobar/Quake III Arena Source Code/
* Biggest patch EVAR. I wonder how many mail boxes this will fill...
* Fix to COM_ParseExt 1 byte overwrite bug
* Fixed some missing calls to trap_FS_FCloseFile
* Fixed q3msgboom and q3infoboom bugs
* Fixed some qboolean type confusion
* Above fixes from http://www.quakesrc.org/forums/viewtopic.php?t=5374
