Re: [Gtk2hs-devel] [Gtk2hs-users] onInsertAtCursor event for Entry

[Duncan C. <dun...@wo...>]

On Mon, 2007-02-12 at 12:28 +0000, Axel Simon wrote:
> On Fri, 2007-02-09 at 19:21 +0000, Duncan Coutts wrote:
> > On Fri, 2007-02-09 at 16:37 +0000, Axel Simon wrote:
> > 
> > > 'onInsertAtCursor' seems to be a very internal signal that is
> > > implemented by the Entry widget before your own onInsertAtCursor handler
> > > has a chance to run. Thus, this signal is rather useless and I removed
> > > it from the the Entry module.
> > 
> > Cheers Axel. Actually there are several signals like this. One of the
> > things I did in the code generator updates I did late last year was to
> > identify these 'action' signals and not bind them. So that'll be one of
> > the things that get fixed in the next development cycle as we re-merge
> > with the output of the code generator.
> 
> That sounds nice. But how do distinguish between 'action' signals and
> useful signals? Do you keep a list somewhere?

That info is (mostly) available from the api xml files. There is a small
list of exceptions where we do want to keep and expose some 'action'
signals:

http://comments.gmane.org/gmane.comp.gnome.language-bindings/813


> > > What you want to use are the functions in Editable which is an interface
> > > that is implemented by Entry. The following program prints the
> > > characters as they are entered:
> > 
> > Nice. Do you want to add this demo to the collection?
> 
> I think that this demo is rather benign and not really worth adding.
> Maybe we should produce a demo program that creates a window with all
> possible widgets and binds each signal so some putStrLn action, so that
> people can look at the code in order to understand what signals are
> emitted when. That's work, though :-0

Or generate it automagically!

ok I'll go away now...   ;-)


Duncan