>I don't think that would do what I am trying to do.
>I want the debugger to keep the code and really
>execute it, but to cursor over it as if it was either
>a function or a single instruction. The way it behaves
>now is that the run cursor doesnt get to the if, it
>goes straight into the macro code, so you cant even
>tell what you are 'if'ing.

This always has been a hassle. I suspect that MPLAB debugger just treats
macros like they are high level language statements, and does not try to
figure out what is inside the statement. I know it has always annoyed me
when stepping through code, and when using Olin's macros, you tend to use a
lot of them.

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body