On Sun, Nov 22, 2009 at 10:28:59PM +0100, Boris 'billiob' Faure wrote:
I've committed some changes to how callbacks are handled in python elementary.
If you use it, your application is now broken, I'm sorry. However,
it's better now than letter :)
So, what have changed?
You used to bind a
Thanks for the important info!
Could you confirm that the change is made in the 43903 revision?
Thanks
cheers
Luca
On Sun, Nov 22, 2009 at 10:28 PM, Boris 'billiob' Faure
bill...@gmail.com wrote:
I've committed some changes to how callbacks are handled in python elementary.
If you use it, your
On Mon, Nov 23, 2009 at 09:58, Vaudano Luca vaud...@gmail.com wrote:
Thanks for the important info!
Could you confirm that the change is made in the 43903 revision?
Thanks
cheers
Luca
It's made in both 43900 and 43903.
--
Boris 'billiob' Faure
Boris 'billiob' Faure a écrit :
On Mon, Nov 23, 2009 at 09:58, Vaudano Luca vaud...@gmail.com wrote:
Thanks for the important info!
Could you confirm that the change is made in the 43903 revision?
Thanks
cheers
Luca
It's made in both 43900 and 43903.
wasn't it possible to add backward
On Mon, Nov 23, 2009 at 20:00, Nicolas Cavallari batch...@free.fr wrote:
wasn't it possible to add backward compatibility, along with a
DeprecationWarning ? That would be less frustrating to users than
having all their apps broken without knowing why.
I thought about it. But it would have
I've committed some changes to how callbacks are handled in python elementary.
If you use it, your application is now broken, I'm sorry. However,
it's better now than letter :)
So, what have changed?
You used to bind a callback to the clicked of a button this way:
bt.clicked = my_func
or
