Re: gEDA-dev: Hooking into selection changes

[Ales Hvezda <ahvezda@xxxxxxxx>]

[snip]
> - It's impossible to make my widget work properly, because I can't get any
>   sort of guarantee that the necessary callback function will be run when =
>it
>   needs to be.

	So, you need to know when the selection changes, or when a specific
object becomes selected/unselected?


>A fairly obvious solution would be to make SELECTION subclass GObject, and
>then to make any function that modifies a selection list emit
>a "selection-changed" signal on it.  Any callback functions could then be
>registered using g_signal_connect() as appropriate.
>
>Anyway, since this would require *extensive* changes to libgeda and gschem,
>I would of course like some indication that it's okay to go ahead with it
>before ploughing in. :)

	I wouldn't be opposed to this, just as long as the overhead of 
subclassing GObject isn't through the roof.

								-Ales

	


_______________________________________________
geda-dev mailing list
geda-dev@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev