The debugger is working again? I gave up asking about it.

On Tuesday, November 3, 2015 at 10:15:39 PM UTC-6, forcesofindia.com wrote:
>
> On top of all of this, have you got yourself the debugger? It may not be 
> as complete as the java debugger in eclipse but it is a very big leap 
> forward from doing cfabort or cfoutput bread crumbing.
>
> np
> On 04-Nov-2015 1:59 am, "Aaron J. White" <[email protected] 
> <javascript:>> wrote:
>
>> Do you still need help with this? If so I can try to give you some 
>> suggestions.
>>
>> On Friday, September 11, 2015 at 12:29:13 PM UTC-5, Caitlin Munley wrote:
>>>
>>> Hi all, I'm a CFML and OpenBD newbie. I'm currently looking into how 
>>> OpenBD handles errors and what debugging information there is available 
>>> during an exception.
>>>
>>> I would really like to see the function name in the tagcontext / 
>>> tagstack, in onError, cfcatch, or GetTagstack(). Right now it only has id, 
>>> line, template, and column. Would it be possible to add it, and perhaps 
>>> additional information like cfc metadata?
>>>
>>> Also, I have a question. Is it possible to set up onMissingTemplate to 
>>> handle .htm / .html and other pages correctly? Some pages we're presenting 
>>> as html pages, but if there's an error it doesn't get caught by onError 
>>> unless the page is a .cfm page.
>>>
>> -- 
>> -- 
>> online documentation: http://openbd.org/manual/
>> http://groups.google.com/group/openbd?hl=en
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Open BlueDragon" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
online documentation: http://openbd.org/manual/
 http://groups.google.com/group/openbd?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Open 
BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to