Re: Gtk::EntryCompletion persists in default behavior after connecting
- From: Krzesimir Nowak <qdlacz gmail com>
- To: Jason Curole <jcurole gmail com>
- Cc: gtkmm-list gnome org
- Subject: Re: Gtk::EntryCompletion persists in default behavior after connecting
- Date: Sun, 10 May 2009 17:38:59 +0200
On Sat, 2009-05-09 at 13:25 +0545, Jason Curole wrote:
> I know this unanswered thread is quite old (so old that I cannot
> figure out how to directly reply to the original message), but I
> recently struggled with this same issue and rather serendipitously
> stumbled upon the solution. So, for future newbies like me and
> Krzesimir if he is still listening, the problem for me (and I believe
> for the code below as well) is that you have to tell 'connect' to
> connect your signal handler to the signal before it connects default
> signal handler. For the example below, that is done as:
>
> m_ref_name_compl->signal_match_selected().connect(sigc::mem_fun(*this,
> &ComplWindow::on_match_selected), false);
>
> Note the false as the second argument to connect. By default this
> argument is true meaning connect after default. And be certain to
> return true so the default handler is not called.
>
> Find out more at:
>
> http://www.gtkmm.org/docs/glibmm-2.4/docs/reference/html/classGlib_1_1SignalProxy0.html#d6c26072ea85fe6e61895b0750421e92
>
>
> Jason
Oh yeah, I figured it myself at last, but I didn't bother myself with
writing a solution. Or forgot to do this, I don't remember. But thanks
for writing this for other people.
Krzesimir Nowak
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]