Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic 1208.19 - Fixes, additions and debug beta 3 (Read 2663 times)
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12071
Location: United Kingdom
Joined: Apr 10th, 2010
1208.19 - Fixes, additions and debug beta 3
Aug 20th, 2012 at 9:03pm
Print Post  
1208.19 has been released along with new debug beta instructions

If you are running the new version of visual micro you should see a new yellow question mark icon on the tool bar next to the arduino boards list. This is a new "Micro Explorer" education system. 

The Micro Explorer provides arduino reference, help and examples along with a special google search of arduino.cc and visualmicro.com.

The Micro Explorer makes it easy to clopy arduino examples into new sketches or simply open for examples for copy/paste into existing sketch code.

The Micro Explorer reference section provides arduino, avr and gcc help documents. Clicking a reference/help document will open the item in your web browser.

The "What's new" section of the Micro Explorer shows a page from the VisualMicro.com site which we will use to inform you of new features.

Most of the new product features are shown in the project properties grid. 

Open source debugger visualizations

Build your own instrument controls to display debug data using any .NET language and drop the resulting dll(s) into the Visual Micro Visualizations Plugins folder.

Digital and Analog Visualizations are included with the upgrade. Full source code will be available on codeplex.



Re-Compile Libraries When Project Macros Change

The next version forces libraries to re-compile when project #defines and macros are changed.

If you are frequently changing macros and are using standard Arduino libraries that do not need to be re-compiled then compilation times can be improved by disabling this feature for a specific project. 

"Project Properties>Macros Affect Libraries=False"

Adding new Arduino files to a project

The default extension of new files (pde/ino) is applied based upon the current arduino version

Adding new Arduino CPP File

The resulting new cpp/h files will contain basic arduino syntax such as #ifndef, simple class definition and #include arduino.h (or wprogram.h) in arduino versions earlier than 1.0). 

An extern object is automatically created within the new .cpp and .h files. 

The name of the object is the UPPERCASE version of the class name or, if the class ends with the text "Class" then the object becomes the class name without the "Class" text. 

For example:
1) User creates a new Cpp called MyButtonClass
2) Visual Micro creates a new .cpp and .h containing a class called MyButtonClass and an object called MyButton. MyButton will be ready for immediate use in a .pde/ino file and will include a single method called init()

Code
Select All
MyButton.init(); 


Opening pde/ino files in an empty visual studio
 
When drag/dropping a pde/ino from window explorer, if there is no solution open in vs, prompt to open/create a new arduino project. Same applies to "File>Open File"

Serial Window

Font Size and Family set from VS Text Editor Properties

New Project Property Options

Micro Debug
Hit Counters Frequency Type (Counter,millis,seconds,hours)

Micro Reporting
I2C Scan at Startup (Auto #incude wire.h)
Read Analog Pins (default 2Hz)
Read Analog PinsFrequency
Read Analog PinsFrequencyType
Read Digital Pins (default 2Hz)
Read Digital Pins Frequency
Read Digital Pins Frequency Type

Added Breakpoint Expression Symbols

@ReportDigital
@ReportAnalog
@ReportI2C

Adding this syntax to the breakpoint "when hit" property will show the values of all digital and/or analogs in the debugger expression watch window. 

This allows us easily compare the difference between the values at different breakpoints and also to force an update of digital and analog values at a specific point in the code


[i]Reminder: The more debug options you switch on, then the more arduino memory that will be used
  
Back to top
WWW  
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint