Excellent! This works great. I have a couple more things for which I can
submit a patch.
1. The "focus" signal handler on the pane which forces focus to the
outgoing entry doesn't allow one to tab and shift tab off the outgoing
text entry, removing it makes things work great for me.
2. It might be nice to also include home and end as keys which are allowed
to be typed into the gtkimhtml.
Thanks so much for doing all this work! I love using Gaim!
On Wed, 28 Jan 2004, Mark Doliner wrote:
> I turned the caret back on for non-editable gtkimhtml widgets. Let me know if
> there is anything else we can do.
> On Wed, 21 Jan 2004 08:57:44 -0700 (MST), Marc Mulcahy wrote
> > Hi All,
> > Is anyone opposed to just having a visible caret all the time, even though
> > the GTKImHTML widget is read-only. That's what my local copy does, and
> > it's easy to do-- just don't set gtk_text_view_cursor_visible in the
> > gtkimhtml_set_editable function.
> > Otherwise, I think f7 would ban acceptable approach, although it
> > would require pressing f7 every time a new conversation window was opened.
> > Marc
> > On Wed, 21 Jan 2004, John B. Silvestri wrote:
> > > On Tue, Jan 20, 2004 at 11:52:47PM -0500, Mark Doliner wrote:
> > > > On Tue, 20 Jan 2004 14:13:13 -0700 (MST), Marc Mulcahy wrote
> > > > > BTW, do you have any thoughts on the visible caret in the
> > > > > conversation log GTKImHTML widget? We need to have a caret that can
> > > > > be moved around with the arrow keys so that folks who can't use the
> > > > > mouse can select/cut/copy text from the conversation log. Would it
> > > > > be acceptable to make the caret visible, and leave the widget read-
> > > > > only. Or possibly make the caret a preferences setting?
> > > >
> > > > I think most of us are against having a preference for showing/not showing a
> > > > preference. We try to avoid having too many preferences. And the
> widget will
> > > > definitely still have to be read only. I think the best solution would
> be to
> > > > have a caret, but only make it visible when the gtkimhtml widget is
> > > > I'm not sure how difficult that would be to do, gtk isn't really my forte.
> > > >
> > > > Anyone have any input?
> > > > -Mark
> > >
> > > How about something like Mozilla Firebird's "F7" -> Caret mode. This
> > > puts a caret in the web page for selection, navigation, and context
> > > sensitive menus (the special Windows context menu key if you're running
> > > *that* OS, and/or Shift-F10 on either [which was copied from M$, BTW --
> > > credit where credit is due :-/]), while maintaining a read-only text
> > > mode. The only little issue I'm thinking about is just the fact that
> > > this is undocumented (I only learned about it in a /. post some time
> > > ago. Above, Mark just pointed to the idea of "having too many
> > > preferences" - similarly we probably want to avoid too many menu
> > > options. I don't know if F7 -> Caret mode is a standard of any
> > > sort, or just a MozFirebird thing, otherwise I would envision a menu
> > > choice "Options->Caret Mode [F7]" (toggle) in the convo window. Just as
> > > there's really no choice about it in MozFirebird, I see no reason to
> > > disable this ability, just make it a toggling choice. You don't want to
> > > be in caret mode when you're typing messages, so I think toggling
> > > between the 2 parts with F7 seems logical to me.
> > >
> > > Cheers,
> > > John
> > >
> > > P.S. If anyone implements this, and decides to put in vi cursor keys,
> > > I'll be forever in awe with you :-D.
> O O Mark Doliner
> \ | mark@...
> \ | http://www.kingant.net
> "There needs to be a better word for weird."