Releases: ironsheep/P2-vscode-extensions
Releases · ironsheep/P2-vscode-extensions
v1.9.6
Minor adjustment to P2 support!
- disable debug output logs (accidentally left this on, oops!)
Full Changelog: v1.9.5...v1.9.6
v1.9.5
Add Signature Help support for P2!
- When typing method calls "signature help" will describe parameters needed, with meaning, as they are typed
- Adds display of parameter and return value descriptions to built-in method hover text
- BUGFIX Semantic P2: flag illegal use of trunc|float|round [with missing ()'s, or no parameter]
Full Changelog: v1.9.4...v1.9.5
v1.9.4
Minor fixes to hover support for P2!
- PRI methods want non-doc-comments vs doc-comments
- Add a blank line before locals in PUB/PRI generated method comments
Full Changelog: v1.9.3...v1.9.4
v1.9.3
Minor fixes to P2 hover support!
- Now handle PUB/PRI inline pasm variables and labels
- Adjust the naming of method parameters, return values, local variables, inline-pasm labels, variables
- Adjust the naming of object variables, methods, labels
- Allow preceding non-doc comments to be multi-line (in addition to single-line) for constants, variables, labels
- Provide missing signatures for float(), trunc() and round()
Full Changelog: v1.9.2...v1.9.3
v1.9.2
New feature: Hover support for P2! (P1 coming soon)
Hovers show information about the symbol/object that's below the mouse cursor. This is usually the type of symbol and description. Feature in README
- Hover over User variables, constants, methods, pasm labels, and objects to display pop-up information about the item including comments within the code for the item
- Hover for Built-in Spin2 methods, variables, constants, and smart-pin constants to display pop-up documentation about the built-in item
- Adds new Doc-Comment Generation for PUB and PRI methods via keystroke [Ctrl+Alt+c] - Ctrl+Alt+( c )omment.
- Comment is inserted immediately below the PUB or PRI line. See examples - BUGFIX P2 no longer treats
asmclk
as pasm label (Oops) - BUGFIX P2 in debug() statements: variables accessed as sub bitfields now highlighted correctly (e.g., c.[2..7])
- P2 syntax: added getcrc, strcopy
- P2 semantic highlight: added missing smartpin constants
What's Changed
- Public new hover feature from Develop branch by @ironsheep in #23
Full Changelog: v1.9.1...v1.9.2
v1.9.1
New feature: Object Hierarchy view for P1 and P2!
- Adds new Object Hierarchy browser when editing spin code
What's Changed
Full Changelog: v1.9.0...v1.9.1
v1.9.0
Minor Semantic updates for P1 and P2 along with new Documentation feature!
- Add documentation generation via keystroke [Ctrl+Alt+d], doc opens on the right side
- Fix highlight of object constant references in case statement selectors P1 and P2 (#17)
- Flag "else if" in spin code as illegal / won't compile - P1 and P2 (#18)
What's Changed
Full Changelog: v1.8.9...v1.9.0
Full Changelog: v1.8.8...v1.8.9
v1.8.8
Minor Semantic fixes for P2
- P2 Add parsing/highlight of new 'field' accessor
- P2 Fix highlight of short variable names within line (offset to var was incorrect)
- P2 Fix highlight of spin-builtin names within debug() lines
Full Changelog: v1.8.7...v1.8.8
v1.8.7
v1.8.6
Spin/Pasm for P1 and P2 - Semantic update
Minor Semantic fixes for P1 and P2
- P1 Repair detection/highlight of multi-line doc comments
- P2 highlight PUB/PRI P1 signatures (without parens) as NEED porting! (color them RED)
- Known Issues w/v1.8.6
Nothing really changed. Here's the recap.
- The single-quote comment (now only on debug statements) is being handled by the semantic (vs. syntactic) parser this is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within trailing line comments on debug lines
- Syntax highlight of DAT section sometimes fails... (although it is less often now...)
- Semantic highlight: the 'modification' attribute is being over-applied, should use more than := as test!!!!
- I'm sure there are more issues... but this is continually getting better!
Full Changelog: v1.8.5...v1.8.6