Typing in the read-only log view should move focus to the text entry

[Marius Gedminas]

Todd Chambery suggests:

> If you select the (uneditable) text in the log view, you have to tab or
> click the text entry to gain focus. When a UI has only a single point
> of text input it's nice to have any keyboard input immediately put to
> use regardless of where the explicit focus is in the application.

I understand that Pidgin's chat windows do something like this.

[Bruce van der Kooij (brucevdk)]

The function in Pidgin which does this is pidgin/gtkconv.c:refocus_entry_cb.

I've tried to make a carbon copy of it in Python (I assumed there would be no more elegant way to do it), but it didn't behave quite the same. I think what I have right now is acceptable, when you type any text in the log_view it will switch focus and pass on the event. The major different with Pidgin is that any text already in task_entry will be deleted, the typed character is not appended.

Relevant discussion on IRC( #pidgin@freenode):

[22:27:27] <khc> unfortunately that doesn't interact well with other input methods
[22:28:19] <Brucevdk> khc: can you elaborate?
[22:29:23] <khc> some input methods require multiple keystrokes to enter one character

[Bruce van der Kooij (brucevdk)]

Sorry, bit tired, forgot to remove some references to Pidgin talk (conversation instead of log view) and keys GTimelog doesn't use (F6/F10) .