[Gambas-user] This is interesting...

[sbungay]

   What is it?

Benoit Minisini wrote:
> On dimanche 29 avril 2007, sbungay wrote:
> 
>>Benoit Minisini wrote:
>>
>>>It seems that a lot of strange things happen on your computer with Gambas
>>>:-)
>>
>>  Yeah... just lucky I guess :-/
>>
>>
>>>Eval() may have a bug, but I can't imagine how the interpreter can
>>>deliberately convert process output to upper case! And what do you mean
>>>by "shutting down and restarting Gambas"? Your project is executed in its
>>>own process, so I don't see what you are talking about.
>>
>>   Shutting down and restarting GAMBAS.. i.e. quitting Gambase so that
>>it is no longer running, then (either from a shell by typing 'gambas2'
>>or from an icon I have on the desktop) restarting GAMBAS, reloading the
>>project by selecting it from the list of recent projects, and running
>>the project.
>>
>>
>>>I think you should be far more precise, otherwise I will never understand
>>>what happens on your machine!
>>>
>>>Regards,
>>
>>   Found another Signal 11 problem, seems related to the Editor control
>>being empty on a form. I will try to be as accurate as possible without
>>writing a small book :).
>>   Reference the project I recently sent you. It is now changed a
>>little, but remains basically the same.
>>   On the CreateCheckPoints form of the Questware project there is an
>>Editor control called 'EditorDescription'. Normally this would be
>>populated from one of the tables, but when the application is newly
>>installed the tables are empty and therefore so is the editor control.
>>No problem, that should be OK, after all we want to use the application
>>to create the data. I start by entering data into the first entry field,
>>which happens to be an editable ComboBox. No problem with that... then I
>>click inside the empty editor control to start entering data into it.
>>*ZAP*! the application seg-faults. Oooookaaaaay.. I restart the
>>application (no I did not quit GAMBAS, I just clicked on the run
>>gadget). I enter info into the first field again, then skip over the
>>editor field and test all the other text boxes, combo boxes, dial
>>controls, and drag and drop functionality... all works OK, so I position
>>the mouse over the editor control and... ->click<- *BOOM* Seg fault.
>>Off I go to the code. I change things so that there is default data in
>>the control at form initialisation (it will get overwritten when real
>>data is available from the tables). I repeat the above steps....
>>->click<-... nothing... it works as it should, no seg-fault.... very
>>strange.... but I have a work around.
>>
>>Steve.
>>
> 
> 
> I think I see what it is...
>