Re: Feature request maybe?

Graham says...

>  Opt-return goes to the first unread tab in that window.  Hitting it 
> again goes to the next, etc...  After all tabs have been read, it 
> goes to the first tab whose user is typing.  If no tabs have typing 
> or unread messages, it does nothing.  This is useful if you are 
> acting like you are stuck in "reply mode" where you are replying to 
> each message as it comes in.  In addition, Cmd-Left Arrow and 
> Cmd-Right Arrow cycles through all conversations just like it 
> always has.

Thanks, Graham! The "hop to an unread tab" feature is VERY cool, and 
saves me a lot of cmd-arrow presses. However, since I'm used to the 
cmd-arrow, and will still need to use it quite a bit anyway, I wonder 
if it would be easy to let me set cmd-something in place of 
opt-return. The latter is a more awkward key combination in general, 
and it's especially awkward since my fingers are used to the command 
key for getting around in Fire.

Actually, cmd-shift-arrows would be a great alternative, as far as 
I'm concerned. My fingers already know how to do that (thanks to 
Safari) and it has the crucial advantage of being a slight variation 
of the cmd-arrow keystroke that Fire users are already using for a 
similar task. (Similar keystrokes for similar activities would make a 
lot of sense.)

Meantime, there've been lots of instances where I've navigated among 
tabs, I'm ready to type at someone whose tab is frontmost, and Fire 
just makes little clunking noises at me when I hit a key. It's 
complaining because the insertion point isn't blinking in the 
text-entry area at the bottom of the window, and yet I'm crazily 
typing along anyway. (How dare I? :-)

Ideally, Fire really should never refuse to let me type. If the Buddy 
window is frontmost and I start typing, Fire helpfully leaps to the 
screen name of a buddy whose name I seem to be starting to type. If a 
chat window is frontmost, and I start typing, it should assume that I 
mean it. Beeping when it could just as easily let me type seems 
mean-spirited! (If I've just selected text in the history pane, OK, 
it's somewhat sensible that the insertion point in the typing area 
could be inactive, but even in this case, that's unnecessary. If all 
I've done is click the window to bring it forward, or used cmd-arrow 
to change tabs or chat windows, let me type.)


==========================================================================
  Mark H. Anbinder, Vice President  |                        mha-/mqabDFo/[email protected]
  Public Communications Inc.        |                http://www.14850.com/
==========================================================================


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Fire-talk mailing list
[email protected]
To unsubscribe or change your options use the web interface:
https://lists.sourceforge.net/lists/listinfo/fire-talk
Have a question? Please read the Fire Frequently Asked Questions:
http://fire.sourceforge.net/faq.shtml