If you have downloaded any of my stuff from the conferences, you will find on most forms a button without a caption that has code that toggles DEBUG ON / OFF. All the eeps have Debug Trace at the beginning of them allowing to start tracing within a reasonable point in time, the eep I want instead of the whole kit and kaboodle....
----- Original Message ----- From: "Alastair Burr" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Sunday, July 03, 2005 2:57 AM Subject: [RBG7-L] - Re: Tracing an eep > Bernie, > > Sure we have a 4th of July - it's tomorrow - we'd all get confused if we > went straight to the 5th! <g> > > Do we celebrate it? Why would we? <g> We have just celebrated T200 though - > 200 years since the Battle of Trafalgar - we won that one! > > I've spent hours (well, a couple of seconds anyhow) trying to figure out the > link with trace in eeps but I've failed. > > The only things that seems anything like what you want is to "Execute to > Error" ( [Shift]+[F10] ) - maybe executions is the link? - and "No Break on > Error" ( [Ctrl]+[F5] ) but it would be really nice to have an easy "trace on > / trace off" command syntax. > > Enjoy your celebrations, > Regards, > Alastair. > > > ----- Original Message ----- > From: "Bernard Lis" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[email protected]> > Sent: Sunday, July 03, 2005 5:10 AM > Subject: [RBG7-L] - Tracing an eep > > >> Happy 4th to all, >> >> 1st question: >> Does England have a 4th of July? >> >> 2nd question: >> I tried to trace an eep by doing this: >> >> original eep name: oDoor.eep >> >> I changed the name in the form to oDoor2.eep >> odoor2.eep consists of: >> trace oDoor.eep >> return >> >> It skips the oDoor.eep entirely and traces the rest of the form eeps. >> >> How do you trace an eep without tracing the entire command file? >> >> And can you turn trace off in another eep? >> >> Bernie Lis >> >
