>>    Button.new("exit") { exit }
>> 
>> I don't care who handles the event when and how or even what it is
>> called. I want the toolkit to take care of that *entirely*.
>> asynchronously, threadsafe.
>
> That is interesting and makes for a very simple interface when you
> want a quick and dirty gui. However, this doesn't work very well when
> there's more than one possible event on a widget. For instance, you
> might have a custom widget to which you want to add both on_hover and
> on_click actions.

Then use the complexer registration method for that.
Simple things do not disable complex things.

+--- Kero ------------------------- kero@chello@nl ---+
|  all the meaningless and empty words I spoke        |
|                       Promises -- The Cranberries   |
+--- M38c --- http://members.chello.nl/k.vangelder ---+