Re: [PyKDE] Lambda function call in connect statement

2001-03-05 Thread Aaron J. Ginn
Phil Thompson wrote: Sorry - I should have noticed this right at the start... The problem is that you are not keeping a reference to the function object that lambda returns - so it is getting garbage collected immediately. The signal is them emitted to an object that no longer exists,

Re: [PyKDE] Lambda function call in connect statement

2001-03-03 Thread Phil Thompson
"Aaron J. Ginn" wrote: Phil Thompson wrote: However, I don't like segfaults - send me a small but complete script that demonstrates the problem and I'll take a look. Phil I've attached a script that displays the core dump. I also included the non-lambda version of the connect

Re: [PyKDE] Lambda function call in connect statement

2001-03-01 Thread Aaron J. Ginn
Phil Thompson wrote: As lambda functions are supposed to be "syntactic sugar for a normal function definition" I don't see how using it helps you. Your function wouldn't be executed until the button click anyway. If I write the connect statement without a lambda as follows:

Re: [PyKDE] Lambda function call in connect statement

2001-03-01 Thread Aaron J. Ginn
Phil Thompson wrote: However, I don't like segfaults - send me a small but complete script that demonstrates the problem and I'll take a look. Phil I've attached a script that displays the core dump. I also included the non-lambda version of the connect statement that shows how the pop-up