Re: [rox-devel] Re: Archive and ROX-Session

[Thomas L. <ta...@ec...>]

On Sun, Mar 14, 2004 at 07:30:06PM +0000, Thomas Leonard wrote:
> On Sun, Mar 07, 2004 at 04:26:42PM +0000, Stephen Watson wrote:
> > Thomas Leonard <ta...@ec...> wrote:
> [...]
> > > I'm not sure I like the button thing... does the clicked value get saved?
> > 
> > The value saved should always be 0, which is why the callback gets called
> > twice.
> 
> Yes, that's what I don't like about it. We're saving something that isn't
> an option, or useful in any way.

I've added a widget_registry dict to OptionsBox, to provide an easy way to
register new option types, and removed build_button in favour of this.

Works like this:

def build_button(box, node, label):
	button = g.Button(label)
	box.may_add_tip(button, node)
	button.connect('clicked', my_button_handler)
	return [button]
OptionsBox.widget_registry['mybutton'] = build_button


For buttons, we can add a convenience function too, of course. Needs
testing...


-- 
Thomas Leonard			http://rox.sourceforge.net
tal00r at ecs.soton.ac.uk	tal197 at users.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1