RE: Changing keyboard bindings

I actually like the balloon help -- it's a great way to learn the keyboard shortcuts. It took me a while to find where the balloon help for the buttons was being created. It's in method create_control_buttons() in srcbar.itcl -- obvious once you get there.

I had some time to experiment with the bind_plain_key calls in srctextwin.itb. I bound F10 and F11 to 'next' and 'step', which works great, however two problems then cropped up:

1) The first time I press F10 it opens up the menus. After that it works as a shortcut, but... weird.
2) I can't map Shift+F11 to Finish. Well, I can't map it at the same time that I have F11 mapped to step. I tried doing the mapping of F11 before the mapping of Shift-F11 but it still doesn't seem to work. Pity.

Getting close however.

-----Original Message-----
From: Keith Seitz [mailto:[email protected]] 
Sent: Friday, February 22, 2013 6:18 PM
To: Bruce Dawson
Cc: [email protected]
Subject: Re: Changing keyboard bindings

On 02/22/2013 06:00 PM, Bruce Dawson wrote:
> I found three places in srcbar.itcl where "accelerator N" is specified 
> -- twice for the Control menu and once for the "trace" menu which I 
> assume is the toolbar with the step and next buttons. However when I 
> change all three occurrences of N to Q and do make/make install it 
> affects the Control menu but not the toolbar.

Gah! Yes, I forgot that those get displayed on the balloon help. Those are in srcbar.itcl, scattered in various places. TBH, I wouldn't care if we deleted the key bindings from being displayed in the balloons. It's a very unusual thing to do. Maybe it made sense to someone a fifteen years ago.

> I also noticed that srctextwin.itb does some binding with 
> bind_plain_key -- it looks like that is what affects what is actually 
> processed, as opposed to what is actually shown.

Doh! Yes, that is where those bindings would be useful, no? I completely spaced on that, sorry.

Keith