keyboard
- From: "Fox, Kevin M" <kmfox bhi010 bhi-erc com>
- To: "'gnome-list gnome org'" <gnome-list gnome org>
- Subject: keyboard
- Date: Fri, 4 Dec 1998 08:05:50 -0800
> Well, there should be a default reserved set of sequences for all
> programs. Hmm.... I think the idea is not getting across exactly like I
> thought. Let me reword it. In microsuck windows there is an underlined
> letter in each menu. you hit alt and then that letter to get that menu. A
> menu item also has an underlined character. you hit that key to activate.
> EX. the File menu has an underlined F letter.
> The Save item has a S underlined. to save quickly you hit alt f s.
> The programmer has full control on what letters to underline, but they
> usually follow f for the file menu, s for the save item, a for save as...
> etc.
> having a hole sequence for an individual item is nice but not necessary.
> using an alt key to get to the menu and using the arrow keys works as
> well.
>
> -----Original Message-----
> From: bratsche@dfw.net [SMTP:bratsche@dfw.net]
> Sent: Thursday, December 03, 1998 6:00 PM
> To: malbright@betasphere.com
> Subject: Re: keyboard
>
>
> This is really great for a single application, but it seems like it would
> be a little awkward for an environment like GNOME. Here's my thoughts:
>
> It would be fine for 'stock' menu items. e.g., you do this for "New.." in
> one GNOME application and it sets it as the key binding for 'stock New'
> menu items. However, you either break the consistency by not providing
> this feature for non-stock menu items (e.g., "Export to PDF" in a word
> processor) or you add code to do that on a per-application basis for all
> GNOME apps, which would require each app to also have to test the binding
> against GNOME's global settings.
>
> Example: say Ctrl-P is the user's binding for GNOME stock "Print" menu
> item. The user goes to "Export to PDF" and hits Ctrl-P. The application
> needs to compare this value against all of GNOME's stock key bindings, and
> when it finds Ctrl-P already occupying the "Print" binding, it'll have to
> remove the "Print" key binding in order to set "Export to PDF".
>
> This is fine, really, except for one thing. Suppose our word processor
> isn't loaded and the user sees that his "Print" binding is empty and tries
> to set it back to Ctrl-P. GNOME can't check key bindings against all
> applications' local key bindings. I suppose this can be worked around
> easily enough by having some sort of dialog warning popup at the
> application's next startup and informing the user that his key binding for
> "Export to PDF" has been removed because its key has been assigned to
> GNOME's global "Print" stock.
>
> It might be a cool feature, but I still think it may be a little awkward
> for an environment like GNOME. Anyone else have an opinion on this?
>
> Cody
>
> On Thu, 3 Dec 1998, Matthew Albright wrote:
>
> > For keybindings in an application (like Alt-Q being quit, or Alt-O
> > being File Open), The GIMP has a really cool way to do it.
> >
> > You pull down a menu with your mouse, and while you are over let's say
> > "File Open... Ctrl-O", you just press the key combination you want to
> > bind with that menu item. So if you press Alt-O, the menu item
> > changes to "File Open... Alt-O", and Alt-O is now your shortcut for
> > File Open.
> >
> > Check it out in The GIMP if that explanation is too opaque.
> >
> > Obviously this does not solve the problem of binding things in all
> > applications, or remapping Ctrl to Alt or something, but it's a start.
> >
> > matt
> >
> > _________________________________________________________
> > DO YOU YAHOO!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> > --
> > FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
> > To unsubscribe: mail gnome-list-request@gnome.org with
> > "unsubscribe" as the Subject.
> >
>
>
> --
> FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
> To unsubscribe: mail gnome-list-request@gnome.org with
> "unsubscribe" as the Subject.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]