Author Topic: [fixed] development: r1801: key binding issues  (Read 2331 times)

james876

  • Guest
[fixed] development: r1801: key binding issues
« on: 5 March 2011, 13:23:04 »
I tested the SVN - 1801, when I press the Keyboardsetup in the game menu button, the button does not respond, and then I found error in the log:

 In [.. \ .. \ source \ shared_lib \ sources \ platform \ sdl \ window.cpp:: Shared:: Platform:: Window:: handleEvent Line: 305] (c) Couldn't process event: [UNKNOWN ERROR] codeLocation = f
« Last Edit: 9 March 2011, 21:36:11 by tomreyn »

titi

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 4,240
    • View Profile
    • http://www.titusgames.de
Re: SVN - 1801 error!
« Reply #1 on: 5 March 2011, 19:39:15 »
I have similar problems:

My son saw that he was no longer able to speedup the game with number block "-".
I told him to go to the options to fix it. He did like I said and set it to "-" there.
When he stated a game and presses "-" now he gets an error message. So he decided to go to the options again, but he cannot enter the keysetup any more.

Any ideas?
Try Megaglest! Improved Engine / New factions / New tilesets / New maps / New scenarios

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: SVN - 1801 error!
« Reply #2 on: 5 March 2011, 21:50:10 »
There's an issue with the keyboard configuration in r1801: if you try to assign a function key (F1..F12) to a key, this comes out as f1..f12 instead of vkF1..vkF12 and is not saved. This may be similar for other virtual key bindings (vk...).
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

ultifd

  • Airship
  • ********
  • Posts: 4,443
  • The Glest Video Guy :) The one and only. :P
    • View Profile
    • My Youtube Channel
Re: development: r1801: key binding issues
« Reply #3 on: 5 March 2011, 21:56:52 »
I think all you need to do is to re-build... I successfully compiled SVN HEAD with no problems.

james876

  • Guest
Re: development: r1801: key binding issues
« Reply #4 on: 6 March 2011, 02:57:24 »
This error exists, re-build does not work. When I run the game the error still exists.
when I press the Keyboardsetup in the game menu button, the button does not respond,
Thank you!

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: development: r1801: key binding issues
« Reply #5 on: 6 March 2011, 03:38:23 »
What exactly are people having trouble with in the keyboard setup? I am able to go in and change keys fine, the f1 is sdl's version of the key where the vk naming convention was something we used internally.. both should work.

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: development: r1801: key binding issues
« Reply #6 on: 6 March 2011, 21:49:08 »
I'm now on r1810 after a full rebuild. When I enter the "Options" menu, then the "Keyboard Setup" menu, and change the key binding for "ChangeFontColor" to "f3" (by pressing the F3 function key), then click on "OK", then click on "Keyboard Setup", no key binding is assigned to "ChangeFontColor" anymore. It does not seem to store these.
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: development: r1801: key binding issues
« Reply #7 on: 6 March 2011, 23:46:09 »
This should work with 1812, thanks

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: development: r1801: key binding issues
« Reply #8 on: 7 March 2011, 00:03:25 »
It does for me. Thank you.
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

MuwuM

  • Ornithopter
  • *****
  • Posts: 426
  • No Game without Move(ment)
    • View Profile
    • MuwuM - Lexicons
Re: [fixed] development: r1801: key binding issues
« Reply #9 on: 8 March 2011, 02:24:48 »
There are still some key's not working correctly ... will have a closer look tomorrow

james876

  • Guest
[fixed] Windows Keyboard SVN Bug(s)
« Reply #10 on: 8 March 2011, 09:31:19 »
I'm sorry to tell you: I changed the key is up CameraModeUp key (with the keyboard arrow keys), but no effect, still show vkup.
I get some error message in the log file.
 The same error also occurred in the vkleft, vkright and vkdown these keys. Thank you!
Code: [Select]
*ERROR* In [..\..\source\shared_lib\sources\platform\sdl\window.cpp::Shared::Platform::Window::handleEvent Line: 304] (c) Couldn't process event: [UNKNOWN ERROR] codeLocation = j
ESC key also has problems...

BTW:Another question: If you change the arrow keys left for the q key, press the q key to move into the game screen, no response.
« Last Edit: 9 March 2011, 21:35:49 by tomreyn »

titi

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 4,240
    • View Profile
    • http://www.titusgames.de
Re: Windows Keyboard SVN Bug(s)
« Reply #11 on: 9 March 2011, 10:00:53 »
How did you change the keys? With the ingame options?
Try Megaglest! Improved Engine / New factions / New tilesets / New maps / New scenarios

ultifd

  • Airship
  • ********
  • Posts: 4,443
  • The Glest Video Guy :) The one and only. :P
    • View Profile
    • My Youtube Channel
Re: Windows Keyboard SVN Bug(s)
« Reply #12 on: 9 March 2011, 10:09:41 »
How did you change the keys? With the ingame options?
Yes, this bug is confirmed by MuwuM and I. Maybe softcoder fixed it with his recent commits, not sure.

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: Windows Keyboard SVN Bug(s)
« Reply #13 on: 9 March 2011, 16:44:00 »
Yes its fixed, another quick with Visual Studio.

james876

  • Guest
Re: [fixed] Windows Keyboard SVN Bug(s)
« Reply #14 on: 10 March 2011, 01:56:15 »

BTW:Another question: If you change the arrow keys left for the q key, press the q key to move into the game screen, no response.

I tested the SVN-1830, but still have this problem. Thank you!

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: [fixed] development: r1801: key binding issues
« Reply #15 on: 10 March 2011, 18:46:18 »
Fixed in svn

 

anything