Strategies for debugging in the iOS Simulator
livfoss at mac.com
Fri Feb 17 11:32:19 CST 2012
Chris, what a fount of knowledge you are! Again, I hadn't realised the Console Application existed - in fact at the time of writing I haven't found it yet, but I dare say I will soon. It is mentioned once in the iOS Deployment Notes and AFAIK nowhere else (tho it might be buried in a lesson somewhere). Useful, anyway.
The way I have been debugging in the interim has been to put a scrolling field in front of my main screen and having a little handler that puts a text string in it - then I scatter calls to this handler around my app. I was doing this anyway for timing and other reasons, but the field wasn't visible except in a special debug mode, so it was fairly easy. The only problem was when my app froze (waiting for the sound to be done - see another of my mails). I couldn't get control of the field so I couldn't scroll it…
One lives and learns. I learned a lot today.
On Fri, 17 Feb 2012 08:15:12 -0700, Chris Sheffield <cmsheffield at me.com> wrote:
>> Debugging is a bit of a pain still. No doubt about that. However, it can be made a bit easier by using simple "put" commands in combination with the Console application. All put statements will output to the console. I find that a little easier to deal with than a bunch of answer commands.
>> Chris Sheffield
>> Read Naturally, Inc.
>> On Feb 17, 2012, at 2:11 AM, Graham Samuel wrote:
>>> Having reached the point where I can run an app in the simulator, I can't find any way of getting any results out of it, apart from adding various displays, 'answer' statements and the like - in other words, I have to distort my app in order to debug it. This is sad, since at this stage the app works fine in the IDE but gets stuck (unresponsive) in the simulator.
>>> Does anyone have any tips or strategies for making the simulator more useful for testing - or have I misunderstood what it's really intended for?
More information about the use-livecode