The new features/improvements included in this version are:

· A Watch Window was implemented, for keeping a list of expressions to be evaluated after processing each debugging command.
· Tooltips are now displayed in the source code viewer when the mouse cursor is over a variable or equate name, displaying the variable name, data type and current value.
· If there is any text selected in the source code viewer and the mouse cursor is over the selected text, awDebugger now evaluates the selected text as a Clarion expression and displays the resulting value in a tooltip.
· Ability of selecting the thread currently in view (the thread whose information is displayed in both the Stack Trace and Registers windows).
· All OutputDebugString calls done from the application being debugged can be optionally forwarded after they are processed and consumed by awDebugger (this allows you to capture them in DebugView from SysInternals, or similar software).
· Ability of specifying command line parameters to be passed on when launching the application to debug.
· Project-specific options from the general Options dialog now can be defined when launching the application to debug (project folder, redirection file, etc.). This options will be remembered the next time you launch the same application from awDebugger.
· Now you can choose which kind of message will be written to the log when a tracepoint is hit (info, warning or error message).
· A new context menu was added to the Global Data and Stack Trace windows with the following options: Locate in Memory Window, Copy value to clipboard, Copy offset to clipboard, Expand all & Contract all.
· The Properties Grid now also displays properties for global and local variables.

Thanks to all awDebugger users for their suggestions!

The truth is that it doesn’t take much time to get used to a time-saver feature and as soon as you got used to it, you start to see how it can be improved to save even more time. We Clarion developers are a bit lazy, and I’m not the exception to that rule so… why should I copy code from the source viewer and paste it into the Immediate Window to evaluate it if we could just tell the debugger to display the results in a tooltip?

That’s how the smart tooltips became a new item on my to-do list for awDebugger, and I am happy to tell you that they are already implemented and will be publicly available in the upcoming v1.1!

Here’s how they work:

• if you place the mouse cursor over a variable name for some time, a tooltip will appear displaying the variable name, data type and current value (for the current thread).
• if the mouse cursor is over a Clarion equate, the value of this equate will be displayed in the tooltip.
• you can also have smart tooltips evaluating more complex Clarion expressions. Just select the text you want to evaluate in the source code viewer, and place the mouse cursor over the selected text.

I hope you enjoy it! I expect this and the rest of awDebugger v1.1 features to be available later this week.

• a Watch Window, for keeping a list of expressions to be evaluated at each step.
• Smart Tooltips, which displays the value and data type of the variables under the mouse cursor in the source code viewer.

I expect these and other features that were requested by our users to be publicly available later this week.

To visit the forums, please click here.

This is just a maintenance release focused in solving most of the issues reported so far, specially those related to the “Step Into Source” command.

You can read more about awDebugger here.

This is just a maintenance release that hopefully solves most of the issues reported by users testing v1.0.0 so far.

Now, Best Dressed… here we go!!

It combines a fully customizable user interface with many advanced features such as conditional breakpoints & tracepoints, syntax-highlighting in both source and assembler code viewers, simplified data viewers, several windows displaying information about the application being debugged, and even an interpreter of Clarion expressions!

Finally we can choose which debugger to use!!!

You can read more about awDebugger here.