Trapping for iOS errors?
MikeKerner at roadrunner.com
Sun Nov 10 17:22:51 EST 2013
in your article, you state that when you are done debugging, you should
comment out the body of the log handler. Why not just change the kdebug
contstant to empty?
On Sun, Nov 10, 2013 at 2:37 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:
> For anyone who'd like more info, I've just posted my RevLive 2012
> conference notes about mobile debugging. It's the top entry in the
> Resources page:
> On 11/9/13 3:57 PM, J. Landman Gay wrote:
>> On 11/9/13 3:53 PM, J. Landman Gay wrote:
>>> On 11/9/13 11:13 AM, JOHN PATTEN wrote:
>>>> Is there any way to catch the iOS error flag and then act on that error?
>>> If you are using the iOS simulator, launch Console and select “All
>>> messages” at the top of the left-side list. To avoid clutter, enter any
>>> distinctive part of your app ID into the filter field at the top right
>>> of the window. Often this is the name of your company or the name of
>>> your app.
>>> If you are debugging on a physical device, launch XCode instead. Under
>>> your connected device, click the Console icon to see the same thing.
>> I forgot: you also need this handler:
>> on errorDialog pErr
>> put pErr
>> end errorDialog
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
and did a little diving.
And God said, "This is good."
More information about the Use-livecode