JJobe at aol dot com
A few days ago I asked for a VBA style variable mouseover function when in
the debugger. I then found a much better way that realbasic has always
handled these nil object exceptions. Try this:
Put exception at the end of the method you suspect may be causing the
problem.
Put a breakpoint after the exception.
Do this for as many methods as you like.
Doing this, captures the nilobject and you can see all the variables at the
time by simply looking at the variables window. Sure helped me a lot.
Remember that the nilobject exception message appears directly below the
line in question - a trap for young players that did me over.
Regards,
Nick
On 29/6/02 3:39 AM, "REALbasic Developer Releases"
<realbasic-dr at lists dot realsoftware dot com> wrote:
> Subject: Elusive NilObjectException
> From: <JJobe724 at aol dot com>
> Date: Fri, 28 Jun 2002 12:44:45 EDT
>
> I have a project that builds/runs fine for Classic, but has never run
> properly with Carbon builds under OS X. Using RB 4.5fc3 and 4.5fc4 I now get
> a message during debug that a NilObjectException error has occurred, but
> there is no indication as to where. This message did not appear when I
> debugged or built for Carbon using 4.0->4.5betas.
>
> I have tried to cut out portions of code thinking I could keep eliminating
> until the problem went away thereby making the problem section of code
> obvious but that didn't work so well. Is there a way to get RB to point out
> to me where exactly the error is occuring?
>
> Thanks,
> John J.
|