James Henstridge <[EMAIL PROTECTED]> writes:
> Christian Reis wrote:
>
> >Would it be correct, according to Python semantics, to pre-copy of
> >the object then? And if so, what are the drawbacks of implementing
> >things that way?
> >
> The drawback is that a number of GTK APIs simply don't work
Christian Reis wrote:
Would it be correct, according to Python semantics, to pre-copy of
the object then? And if so, what are the drawbacks of implementing
things that way?
The drawback is that a number of GTK APIs simply don't work if you copy
the boxed arguments. We used to copy boxed argum
On Sun, Feb 23, 2003 at 05:32:25PM +0800, James Henstridge wrote:
> >behavior of event objects in PyGTK2. The sample program below connects
> >to the button press, motion and release events and stores the event
> >object of the button_press event in an instance variable. In the motion
> >event hand
Bernhard Herzog wrote:
While porting Sketch to PyGTK2 I came across a strange change in the
behavior of event objects in PyGTK2. The sample program below connects
to the button press, motion and release events and stores the event
object of the button_press event in an instance variable. In the mo
While porting Sketch to PyGTK2 I came across a strange change in the
behavior of event objects in PyGTK2. The sample program below connects
to the button press, motion and release events and stores the event
object of the button_press event in an instance variable. In the motion
event handler the
