Re: [gtkmm] custom cellrenderer bug

[Peter Gasper <pgasper designadvantage com>]

What was needed was the entry->grab_focus call within
ComboEditable::start_editing_vfunc(). I had thought I needed to make the
grab_focus call and had tried it in a couple places to no avail, just
hadn't tried that function.

Thanks.

On Fri, 2003-08-08 at 06:08, Markus Gerwinski wrote:
> Peter Gasper wrote:
> > The above was the most helpful. However there seems to be a bug in it which is also
> > present in my attempts at custom cellrenderers. If one selects
> > a combo cell and hits enter it changes to its editable state. But if you want to use
> > the keyboard keys up/down to navigate it you are forced to click on it,
> > otherwise it arrows out of that cell. Nor can you type in the combo until you physically
> > click it with the mouse.
> 
> Maybe my version of a CellRendererCombo can help you here... It's somewhat
> different from the approach in the example, since I encapsulate a Gtk::Combo
> instead of combining an entry and a separate dropdown window to emulate one. I
> attached the sources to this mail. (Don't wonder about the namespace -- The
> files are part of a library I will completely upload to my web site as soon as
> it's ready.)
> 
> However, you'll have to be careful with your signal handling, since the
> "edited" signal is already sent when you open the dropdown list. (It's a
> feature of the Gtk::Entry.) You'll have to use the signals of the combo itself
> (the get_entry()'s "changed" signal or the get_list()'s selection signals), and
> they're messy to use.
> 
> HTH
> 
>   Markus
-- 
Peter Gasper <pgasper designadvantage com>