Hi David,

Thanks for the message.

If you are using the automatic digital report then it is updated at the start of the loop(). Your code has set the pins HIGH and then LOW again before it reaches the end of the loop()

An alternative is to switch off the digital report project property and use one of the break-point 'when hit' special {variables}. I think the one you need is:-
 
{@ReportDigital}

Using the special variable names in the code to force a refresh allows you to use breakpoints in more intelligent locations than simply one at the start of the loop.

I recommend switching off the project property because the digital reports are quite large and some pc's struggle with the volumn of data during debug. If you are using breakpoints that pause then this might not be an issue and both systems can be used together. 

By the way you can also use std expressions in watch statements which can be useful to monitor just one or two pins. Example of a "when hit" that watches pins 13 and 3 + get a digi report

{digitalRead(13)}{digitalRead(3)}{@ReportDigital}

If you use then when hit message to watch variables then remember to un-tick continue execution if you still want the breakpoint to break.

Another way to use the when hit is to make useful messages. In this example an output message is printed but the digiReport is displayed in the digital pins viewer.

The lights are : {digitalRead(13)}, Button pressed: {digitalRead(3)}{@ReportDigital} 

Great thanks for the update, we will try to improve the docs

Don't forget that VS stores break-point info in the solution and not with the project. I find that quite annoying. We must save your solution when closing and for "peace of mind" after making significant changes to break-point settings.

Hi,

The version of Visual Micro in the Atmel Gallery from 10th dec 2014 has a bug. 

Please upgrade to the latest release via visualmicro.com and always worth keeping an eye on the Release History. This was fixed 20th dec and we hope to push a new gallery version shortly.

Thanks