[futurebasic] Re: [FB] calling non-existent buttons/edit fields

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : September 2012 : Group Archive : Group : All Groups

From: Bernie <fblist.bw@...>
Date: Fri, 21 Sep 2012 19:40:55 +0100
Brian wrote:

> 
> On Sep 19, 2012, at 5:37 AM, Bernie <fblist.bw@...> wrote:
> 
>> Doug Stemen wrote:
>> 
>>> I sincerely appreciate the continuing effort to improve FB
>>> 
>>> I am a having a problem with very large FB 4 programs converted to run in FB5. If there are calls to buttons or edit fields that do not exist, there is no indication in FB 5. At seemingly random points these calls result in the compiled program quitting (the calls appear to be damaging RAM data) . In FB4 I could get a warning about these calls if the program was run rather than built.
>>> 
>>> Is there a way that FB5 can alert me about calls to non-existent buttons & edit fields?
>>> 
>> 
>> Currently, if we issue a button or appearance button statement when a button does not already exist, a new one is created. If the button type is not specified, it defaults to push button. Once a button type has been set, it cannot be changed to another type.
>> 
>> One quick way around it may be to abort button creation if a type is not specified. Unfortunately, this may break apps that rely on the default feature.
>> 
>> Please try this update to AppThings.c.
> Doug,
> 
> When you’ve had a chance to test this out, please post back with your experience. Another ( not on the list ) FBer is also seeing intermittent crashes which might be rooted in non-existent buttons too. Your insights would be appreciated and probably helpful.
> 

Don't forget that the update I posted may break apps that rely on the if-you-don't-specify-a-button-type-it-defaults-to-push-button feature of FB.