Two small problems (Debian Squeeze)

[Radek]

Small problem #1, setting keyboard shortcuts. I have seen that I can use two "shift" keys, like Ctrl-Shift-C. But I am not able to set such combination in Editor settings. The first "shift" pressed always wins: I get ether Ctrl-C or Shift-C. I tried to play with "Input Methods" but without success.

Q: Is it possible to specify key combinations like Ctrl-Shift-C by a user?

Small problem #2: The editor window seems to show the undo stack in a line between the line numbers and the edited code. The brown and green marks can be removed by "Clear History" but, of course, next action in the editor window will create new marks. I'd rather not have these marks in the editor window. Most likely, I need to change some colors somewhere.

Q: Is it possible to get rid of history marks in the editor window? How?

Debian Squeeze 6.0.2, Gnome
Code Blocks 10.05

[Jenna]

Small problem #1, setting keyboard shortcuts. I have seen that I can use two "shift" keys, like Ctrl-Shift-C. But I am not able to set such combination in Editor settings. The first "shift" pressed always wins: I get ether Ctrl-C or Shift-C. I tried to play with "Input Methods" but without success.

Q: Is it possible to specify key combinations like Ctrl-Shift-C by a user?

You can add user specific shortcuts to any C::B menus and menuentries, you can reach from the main menu, with the keybinder-plugin (part of the contrib-plugins).
Ctrl+Shift+C is bound to "Edit->Comment" per default.
"Settings -> editor -> keyboard shortcuts"

Small problem #2: The editor window seems to show the undo stack in a line between the line numbers and the edited code. The brown and green marks can be removed by "Clear History" but, of course, next action in the editor window will create new marks. I'd rather not have these marks in the editor window. Most likely, I need to change some colors somewhere.

Q: Is it possible to get rid of history marks in the editor window? How?

Uncheck "Settings -> Editor -> Margins and caret -> Use changebar".

[Radek]

(1) That's exactly how I set my accelerators:  Editor -> Settings -> Keyboard Shortcuts -> select shortcut -> put cursor in the "set shortcut" field and press the wanted key combination. Attempting Ctrl-Shift-C always resulted in Ctrl-C or Shift-C depending on what shift I happened to press first. No problems with setting keys with only one shift. I have Sony Vaio VGN-BX297XP notebook.

(2) The changebar: Solved. Thanks, Jens 

[Jenna]

(1) That's exactly how I set my accelerators:  Editor -> Settings -> Keyboard Shortcuts -> select shortcut -> put cursor in the "set shortcut" field and press the wanted key combination. Attempting Ctrl-Shift-C always resulted in Ctrl-C or Shift-C depending on what shift I happened to press first. No problems with setting keys with only one shift. I have Sony Vaio VGN-BX297XP notebook.

Now I understand.
Your first post did not show me clearly, that the problem is in the keybinder-plugin.

If I remember correctly,thare have bben a recent commit, that changes keybinder behaviour related to Shift-key.

It seems to work correctly in trunk and therefore in the nightlies.
You can try a nightly from my repo.

[Radek]

No change. I have installed the keyring, I have updated sources list and updated CodeBlocks to svn 7419 but attempting Ctrl-Shift-C (or ctrl shift something else) results in Ctrl-C or Shift-C still. Supposing the "ctrl-shift" works elsewhere okay, it must be my keyboard.