[Gambas-user] Signal #11

[Joachim Ruoff]

Hi all,

I had a similar problem, my application runs well until I update to 
Gambas 2.8, then I get the error message with signal#11

I could solve that problem, when I delete the shortcuts in the menu 
editor, now the program runs well. May be there is a bug with that 
shortcuts?
When I use these shortcuts in an other application the same problem occurs.

Regards
Joachim

Hans-Martin schrieb:
> Am Sonntag, 7. September 2008 16:44:34 schrieb Ron_1st:
>   
>> On Sunday 07 September 2008, Hans-Martin wrote:
>>     
>>>> Hello all,
>>>>
>>>> i have an application running well with 2.7.0 but getting a signal#11
>>>> with 2.8.2
>>>>
>>>> PUBLIC SUB ButtonPartner_Click()
>>>>   DIM hForm AS FPartnerStart
>>>>
>>>> signal#11 -->  hForm = NEW FPartnerStart(BenutzerID)    <-- signal#11
>>>>   hForm.Show
>>>>
>>>> END
>>>>
>>>>
>>>> As i get the error by creating a new form (what is designed with the
>>>> gambas-ide) i thing there is 1 component that makes the trouble. But in
>>>> this form i use a bunch of different component, so its not that simple
>>>> to find out what will bring this error.
>>>>
>>>> Any suggestion how to find the guilty component?
>>>>
>>>> regards,
>>>> HMB
>>>>         
>> You get the error on creating the instance as shown.
>> Two things happen
>> 1) building the form as visible object
>> 2) running the initialize code in the class file.
>>
>> If the form has the error you should get the error if the *.class
>> file is empty or a dummy that does nothing.
>> If no error occurs then it is the class file that has something wrong.
>>
>> Just something I had once in the past. At the time MoveScale was introduced
>> in the forms I had some problems alike this.
>> I made the 4 values round values instead float as I see in your form.
>> In my project the bug was gone. Not nessasary this still happens nowadays.
>>
>>     
>>> { Form Form
>>>   MoveScaled(13.4444,4,97,77) <-- to MoveScaled(13,4,97,77)
>>>   Text = ("Partnerverwaltung")
>>>   { EditImmerAn Menu NeuenPartnerAnlegen
>>> ....
>>>       
>
> fixed this, but same behavier  :(
>
>   
>> Second point I see is the percent in the tooltip.
>> Maybe that is a special character in gambas as the \ is.
>>
>>     
>>>   { ComboBoxPartnerName ComboBox
>>>     MoveScaled(11,4,84,3)
>>>     ToolTip = ("'%ter' - findet alle Partner, die 'ter' im Namen
>>> haben\n'May' findet alle Partner, die mit 'May' anfangen")
>>>    Drop = True
>>>     Text = ("")
>>>   }
>>>       
>
> fixed this too, but still sig11
>
>   
>> You could try to make a copy of the project with only the form and class
>> file. Set the form/class as startup and check what happens.
>>     
>
> good idea. i have done this. gambas throws the signal#11 error before the 
> first statement (in _new()) is reached. so the breakpoint i set on the first 
> instruction is never reached... strange. there must be something else in 
> the .form-file that will raise this error...
>
>   
>> Editing here will not corrupt your current real project to mess.
>>
>>
>>     
>
> Many thanks for that. me have to look closer and try more out  :(
> It must something that changes between 2.7.0 and 2.8.2...
>
>   
>> Best regards
>> Ron_1st
>>     
>
> Hans-Martin
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Gambas-user mailing list
> Gambas-user at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gambas-user
>
>