On 11/02/2016 05:19 PM, pozzugno wrote:
> It seems pyGObject implementation gives only two "handler block"
> functions: handler_block(), that needs the handler_id that I don't have;
> handler_block_by_func() that needs the callback to block (the same
> problem of your solution, because I have
Il 02/11/2016 18:55, Nicola Fontana ha scritto:
Il Wed, 2 Nov 2016 14:40:58 +0100 Pozz Pozz scrisse:
2016-11-02 11:24 GMT+01:00 Nicola Fontana :
...
you don't necessarily need the handler id. In C (I don't use
python) you could write the following:
void
Il Wed, 2 Nov 2016 14:40:58 +0100 Pozz Pozz scrisse:
> 2016-11-02 11:24 GMT+01:00 Nicola Fontana :
> > ...
> >
> > you don't necessarily need the handler id. In C (I don't use
> > python) you could write the following:
> >
> > void my_set_value(GtkSpinButton
Il Wed, 2 Nov 2016 10:23:44 +0100 Pozz Pozz scrisse:
> ...
> How do you implement the generic function _my_set_value()? It should have
> two parameters: spinbutton and value. signal_handler_block() function needs
> the handler_id associated that I don't have.
> Maybe during
Il Wed, 2 Nov 2016 00:09:29 +0100 pozzugno scrisse:
> ...
> A simple and clear sequence of instructions:
>
>_set_value()
>_set_value()
>..
>
> will be transformed in a complex, long and cryptic sequence of
> instructions:
>
>_block()
>_set_value()
>