All notable changes to the "avr-utils" extension will be documented in this file.
- Fix error where commands like "Create New Project" in the command palette claim that they are missing ( Would happen especially on VSCode version < 1.75 ).
- Added a progress bar when downloading the toolchain, so that you (the user) are aware of the process.
- Better error message diagnostics, the extension was really lacking in this area as compilations were not giving useful error messages in case errors existed.
- Added necessary configurations to allow VSCode's keybinds
Ctrl+/
andAlt+Shift+A
to quickly comment and uncomment lines and blocks of code respectively. - There was also a (slightly annoying) visual bug where the compile button would render at ALL times. This has also been fixed.
- Changed the quick action for compiling from
F5
toF4
because F5 is usually used for debugging. - Moving from manual builds of minified js file to a CI based workflow (Thank you, GitHub Actions!)
- Refactored Code to get the proper list of devices directly from
io.h
file in the avr toolchain. #3 - Find the list of devices and their files from
out/storage/device_and_file.json
. It's generated using the python script fromsrc/storage/getDevices.py
(you may need to check it from thedev
branch)
- Added an icon
- Readme now uses GIFs so it's compatible with Marketplace
- Added a language "
avr-c
" to thecontributes.languages
section of the package.json file, so that the extension does not conflict with "ms-vscode.cpptools
". - Added a language "
asm
" to thecontributes.languages
section of the package.json file, so that the language can be recognized by the extension. - Updated the code such that the providers in
./src/providers
handle avr-c instead of c. - Updated the code to work better with assembly files (
.s
and.asm
) - Added
.h
files as an alias toavr-c
as well, to prevent logging errors fromms-vscode.cpptools
- Created syntax highlighting for both
asm
andavr-c
to present code better to a user. - Added a setting (user can change it from VSCode settings) that always pops up the terminal during each build. This is especially useful to check for build errors since the terminal output is inaccessible to extensions.
- Initial release