Arghhh. Is this stack corrupt?

[Gerry Orkin]

Yeah error tracking in iOS is a pain. I'll do as you suggest and try to get to the bottom of this. 

Thanks

Gerry


-- http://gerryorkin.com

On 30/03/2011, at 9:08 AM, BNig <niggemann at uni-wh.de> wrote:

> Gerry,
> 
> it is difficult to guess what is happening.
> 
> One thing that happened to me was that I wrote out a file to "documents" and
> then I changed the app and tested in the Simulator and the iPhone and the
> file was not what I expected. It turned out that the file saving was broken
> but the file in "documents" was never replaced when I tested a new version
> of the app. This is because when updating the app in the simulator or the
> device the documents folder is NOT replaced.
> 
> You could try to delete the app from the Simulator before you test a new
> version and add a timestamp to the text of the file to see when it was
> written. the long time or somesuch.
> 
> Of course this might not apply to your situation which shurely sounds
> strange.
> 
> Also I found it very helpful to add temporarily a backgroundgroup with a
> field "fErr" to every card of the stack and have a handler in the stack
> script
> ---------------
> on errorDialog
>   put  the params into field "fErr"
> end errorDialog
> -----------------
> (from one of the example stacks)
> 
> iOS specific code can fail silently and the rest of the code is not
> executed. A great source of confusion.
> 
> Kind regards
> 
> Bernd
> 
> --
> View this message in context: http://runtime-revolution.278305.n4.nabble.com/Arghhh-Is-this-stack-corrupt-tp3414863p3416426.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
> 
> _______________________________________________
> 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