Comment 3 for bug 260288

OK, this one is *really* strange:

on-leave="myOpa(self, 0.999, 0.6)" => WORKING
on-leave="myOpa(self, 1.0, 0.6)" => error
on-leave="myOpa(self, 1.01, 0.6)" => error
on-leave="myOpa(self, 1.02, 0.6)" => error
on-leave="myOpa(self, 1.021, 0.6)" => WORKING

and still (see comment #1): changing on-leave and on-enter is working fine.

OK, just some debugging output to narrow it down (TargetImage.py, lines 172+ changed to):
-----
        self.__widget.render(imgwidth, imgheight, opacity, saturation)
        self.__current_width = imgwidth
        self.__current_height = imgheight
        self.__current_opacity = opacity
        self.__current_saturation = saturation
        print "Opacity: "+str(opacity)
        print "Saturation: "+str(saturation)
        print "Width: "+str(imgwidth)
        print "Height: "+str(imgheight)+"\n"
-----

Is guess this shows when the error occurs:

On startup:

Opacity: 1.0
Saturation: 1.0
Width: 48
Height: 48

Using on-leave="myOpa(self, 1.02, 0.6)", moving in and out:

Opacity: 1.0
Saturation: 1.0
Width: 96
Height: 96

Opacity: 0.6
Saturation: 1.0
Width: 48
Height: 48

Using on-leave="myOpa(self, 1.021, 0.6)", moving in and out:

Opacity: 1.0
Saturation: 1.0
Width: 96
Height: 96

Opacity: 0.6
Saturation: 1.0
Width: 49
Height: 49

And using on-leave="myOpa(self, 0.999, 0.6)", moving in and out:
width and height are set to 47.

So it looks likeeverything is fine when width and height get a new value.

Still wondering why changing on-enter and on-leave (see comment #1) is working though...