[Gambas-user] Sig 11 with menu items remains

[Ian Haywood]

2011/1/3 Benoît Minisini <gambas at ...1...>:
>> Hi Benoit/List:
>>
>>
>> A reminder prior to the release that that annoying Sig11 bug remains with
>> the menu items, you'll remember I tried to use valgrind with it some time
>> ago without success and I think the suggestion was that maybe it is
>> related to a QT4 bug.
>>
>> Maybe someone else on the list is aware of this or can help.
>>
>> I've emailed Ian, who is much more switched on than me about computing to
>> see if he can liase with you on this.
>>
>> Also lately I've been getting some Sig11 with Result objects, not sure why,
>> just to let you know they exist, I'll try and track these down.
>
> If you want to help tracking these bugs, compile Gambas with optimizations
> disabled (run 'make "CFLAGS=-O0 -g" "CXXFLAGS=-O0 -g"' instead of just
> 'make'), and enable core dumps. Then, as soon as you get a crash, a core file
> will be generated, and by using gdb on it, you will get a backtrace of the
> crash you can send me.
Ok, will do.

> I don't want to remove the current Spacing property. But I could add the old
> one if someone find a good name for it. I have already used "Margin",
> "Padding, and "Spacing". Internally, the old spacing property is there. It's
> just a matter of finding a good name!
PixelSpacing?

> Just don't use Collection and create your own container class that fits your
> needs.
while the Collection.Add() loophole remains we are sweet. :-)
but point taken, we will switch to a class emulating Collection using _get/_set

Ian