Re: [gtk-list] Re: Problems with Rulers in gtk--

[Tero Pulkkinen <terop students cc tut fi>]

Oliver Freyd <freyd@uni-muenster.de> writes:
> connect(drw_area.motion_notify_event,hruler.motion_notify_event);
> 
> but gcc says:
> 
> /usr/local/include/gtk--sig.h: In function `class Connection connect(class
> Signal_proxy1<int,Gtk_Widget,_GdkEventMotion *> &, class
> Signal_proxy1<int,Gtk_Widget,_GdkEventMotion *> &)':
> /usr/local/include/gtk--sig.h:1341: no matching function for call to
> `Concretegtkslot1<int,int (*)(_GdkEventMotion *),_GdkEventMotion
> *>::Concretegtkslot1<int,int (*)(_GdkEventMotion *),_GdkEventMotion *>
> (Signal_proxy1<int,Gtk_Widget,_GdkEventMotion *>)'
> /usr/local/include/gtk--sig.h:1099: candidates are: Concretegtkslot1<int,int
> (*)(_GdkEventMotion *),_GdkEventMotion *>::Concretegtkslot1(const
> Concretegtkslot1<int,int (*)(_GdkEventMotion *),_GdkEventMotion *> &)
> /usr/local/include/gtk--sig.h:1099:                 Concretegtkslot1<int,int
> (*)(_GdkEventMotion *),_GdkEventMotion *>::Concretegtkslot1(int
> (*)(_GdkEventMotion *))
> make: *** [colorbutton.o] Error 1
> 
> I don't know what that means, maybe one of my stupid errors,
> something is missing in gtk--...

There was two errors in one of gtk--'s connect() function
implementations handling this situations. I'll release new gtk-- later
today and this bug has been fixed in that release.

-- 
-- Tero Pulkkinen -- terop@modeemi.cs.tut.fi --