mobileControlDelete doesn't work

[Bob Sneidar]

It is not a bug. It is the way ID's work. The ID of the stack itself is not really an ID at all, but a next object ID counter. Whenever you create an object, it gets the stack ID and the stack ID is incremented by 1. This of course assumes there is not an object already with that ID in which case the ID will become the next unused ID, and the stack ID will be assigned one higher than that. As always, my explanations are subject to correction by those more qualified. 

Bob


On Jul 17, 2012, at 9:16 AM, Rick Harrison wrote:

> Hi there,
> 
> mobileControlDelete and iphoneControlDelete do not
> work properly.
> 
> On one card, I created a scroller field which works just fine.
> When I use the closeCard to execute the mobileControlDelete
> the result content reports empty. I created a button to confirm that
> this process is really what is going on.  The control stops working 
> as one would expect, however when proceeding to the next card 
> which also creates a new scroller, the id of the new scroller field 
> reports as being 2, which indicates that the first scroller was never
> deleted.  Of course as one goes from card to card the id keeps
> increasing because none of the controls are really getting deleted.
> 
> Could someone please point me to some example code which
> really deletes the scroller control or confirm to me that this is a
> serious bug please?
> 
> Supposedly this was an old bug that was fixed back in 4.5, but
> it sure doesn't seem fixed to me.
> 
> Thanks in advance!
> 
> Rick Harrison
> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode