Why no single key shortcuts?

Brett Holden wrote on Sun, 24 November 2013 14:20

If Eagle were to require the user to click within the command box

before

entering command line text

No, no, no.  Absolutely not!!!

One of the important features of a command line is that it is quicker and

easier to type a command than to have to use the mouse and click something.

Having to use the mouse to enable the command line makes no sense as it

would completely defeat this.

Also, there are already plenty of keyboard shortcuts.  F1-F12 give you 12

single-key shortcuts.  Then there are many more that require only a single

modifier key, like CTRL or ALT for the alphabetic keys and CTRL, ALT, and

SHIFT for the F-keys.  That already totals 100 single or single-modifier

shortcuts.  There is no problem to solve here.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Brett Holden wrote on Sun, 24 November 2013 14:20

If Eagle were to require the user to click within the command box

before

entering command line text

No, no, no.  Absolutely not!!!

One of the important features of a command line is that it is quicker and

easier to type a command than to have to use the mouse and click something.

Having to use the mouse to enable the command line makes no sense as it

would completely defeat this.

Also, there are already plenty of keyboard shortcuts.  F1-F12 give you 12

single-key shortcuts.  Then there are many more that require only a single

modifier key, like CTRL or ALT for the alphabetic keys and CTRL, ALT, and

SHIFT for the F-keys.  That already totals 100 single or single-modifier

shortcuts.  There is no problem to solve here.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

On 11/24/2013 03:37 PM, Olin Lathrop wrote:

Brett Holden wrote on Sun, 24 November 2013 14:20

If Eagle were to require the user to click within the command box

before

entering command line text

 

No, no, no.  Absolutely not!!!

I agree with Olin, but for different reasons.

I use some applications that have single-key shortcuts, like Mozilla

Thunderbird. If I accidentally get my focus in the wrong window, any

typing causes seemingly random and often catastrophic results that are

very hard to undo, like marking all my unread messages as read, or

archiving messages. It took me quite some time to find a plug-in that

would allow me to disable all of the single-key shortcuts and put an end

to the madness.

On 11/24/2013 11:55 PM, Reece R. Pollack wrote:

On 11/24/2013 03:37 PM, Olin Lathrop wrote:

Brett Holden wrote on Sun, 24 November 2013 14:20

If Eagle were to require the user to click within the command box

before

entering command line text

 

No, no, no.  Absolutely not!!!

Olin is absolutely correct here.  Bad idea.

There are plenty of single keys and one-modifier keys for quick

functions.  The more rarely used functions can be typed quicker than

mouse clicking your way through pull-down menus.

Time this as an example:  Change the width of multiple traces to a

common value, say, 32 mils.  Try it with the click-right context menu,

then again with the Change pull-down menu, then finally with text.  With

text it's "ch wid 32".

If you must do something as drastic as this, at least give me a

parameter setting that I can put in ~/.eaglerc to revert to the current

behavior.

I agree with Olin, but for different reasons.

 

I use some applications that have single-key shortcuts, like Mozilla

Thunderbird. If I accidentally get my focus in the wrong window, any

typing causes seemingly random and often catastrophic results that are

very hard to undo, like marking all my unread messages as read, or

archiving messages.

This has happened to me numerous times.

It took me quite some time to find a plug-in that

would allow me to disable all of the single-key shortcuts and put an end

to the madness.

Drifting off-topic a bit, what was the name of this plugin?

Thanks,

    - Chuck

On 11/25/2013 07:58 AM, Chuck Huber wrote:

On 11/24/2013 11:55 PM, Reece R. Pollack wrote:

I agree with Olin, but for different reasons.

 

I use some applications that have single-key shortcuts, like Mozilla

Thunderbird. If I accidentally get my focus in the wrong window, any

typing causes seemingly random and often catastrophic results that are

very hard to undo, like marking all my unread messages as read, or

archiving messages.

 

This has happened to me numerous times.

 

It took me quite some time to find a plug-in that

would allow me to disable all of the single-key shortcuts and put an end

to the madness.

 

Drifting off-topic a bit, what was the name of this plugin?

It's called "keyconfig". Here's a link to a blog entry (not mine) that

describes it:

http://kb.mozillazine.org/Keyconfig_extension

Once it's installed you can go to the Add-ons Manager, click

Preferences, and you'll get a pop-up that lists all the possible actions

and the currently configured shortcut key. It's a bit laborious to

disable those you don't want, but you only have to do it once. Just make

sure you don't blindly disable those you probably want to keep, like

CTRLC for Cut, CTRLV for Paste, etc.

Am 25.11.2013 13:58, schrieb Chuck Huber:

Olin is absolutely correct here.  Bad idea.

Yes. Quite bad for the 'power user': Having to click completely defeats

the idea of the command line (which I use OFTEN).

If you must do something as drastic as this, at least give me a

parameter setting that I can put in ~/.eaglerc to revert to the current

behavior.

Yes. Either leave the command line unaltered as is, or at least

implement the possibility to make it behave unaltered via an option.

Andreas Weidner