From: Bruce Dawson <bruced@valvesoftware.com>
To: 'Keith Seitz' <keiths@redhat.com>
Cc: "insight@sourceware.org" <insight@sourceware.org>
Subject: RE: Changing keyboard bindings
Date: Tue, 26 Feb 2013 00:51:00 -0000 [thread overview]
Message-ID: <2AC155A009400B4C8B05D518E4819AEF0719DB37@exchange10.valvesoftware.com> (raw)
In-Reply-To: <512826C4.7040500@redhat.com>
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:keiths@redhat.com]
Sent: Friday, February 22, 2013 6:18 PM
To: Bruce Dawson
Cc: insight@sourceware.org
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
prev parent reply other threads:[~2013-02-26 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 0:33 Bruce Dawson
2013-02-23 0:52 ` Keith Seitz
2013-02-23 2:00 ` Bruce Dawson
2013-02-23 2:17 ` Keith Seitz
2013-02-26 0:51 ` Bruce Dawson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2AC155A009400B4C8B05D518E4819AEF0719DB37@exchange10.valvesoftware.com \
--to=bruced@valvesoftware.com \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).