v1.7.3

Spin/Pasm for P1 and P2 - Tabbing update

Minor update to Extension Settings

• Add Named TAB configurations (select between Propeller Tool, IronSheep, or your own custom User1 tabs)
• The extension default is Propeller Tool
• The IronSheep configuration is derived from Propeller Tool but realigned to "tabstop: 4" (every 4 spaces)

- Known Issues w/v1.7.3

Nothing has changed here. Here's the recap.

• We haven't yet learned how to control the ending position of the edit cursor. So in many cases when using selection not an insert point the cursor may end up not being where you might expect it to be after pressing TAB or Shift+TAB. We are looking into how to solve this. Even tho' this problem exists the formatting ability this new service provides is well worth this minor headache. We will keep looking for a means to get this under control.
• 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!!!!

v1.7.2

Spin/Pasm for P1 and P2 - Highlighting Update

Update Spin highlighting (syntax and/or semantic parser fixes)

• Spin: Recognize label or data declaration on the DAT line
• Spin: Recognize non-float decimal numbers with exponents

Update Spin2 highlighting (syntax and/or semantic parser fixes)

• Spin2: Recognize label or data declaration on DAT line
• Spin2: Recognize non-float decimal numbers with exponents
• Spin2: Recognize debug_main and debug_coginit compile time directives
• Spin2: Recognize event names in pasm2 correctly
• Spin2: Fix cases where debug used without parenthesis causes the extension to crash
• Spin2: Recognize coginit constants (some pasm2 cases were being missed)
• Spin2: Add recognition of LutColors directive in debug statements with run-time terminal assignment
• Spin2: Recognize modcz operand constants

- Known Issues w/v1.7.2

Nothing has changed here. Here's the recap.

• We haven't yet learned how to control the ending position of the edit cursor. So in many cases when using selection not an insert point the cursor may end up not being where you might expect it to be after pressing TAB or Shift+TAB. We are looking into how to solve this. Even tho' this problem exists the formatting ability this new service provides is well worth this minor headache. We will keep looking for a means to get this under control.
• 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!!!!

We wish to thank Jay B. Harlow for his contribution to this new feature!

Thank you, Jay, your work is much appreciated!

v1.7.1

Update to keyboard mapping: All key mapping is now reenabled and Align mode is now fully functional

• Fixed: Backspace and Delete are now working correctly in Align Mode
• Fixed: Oops, now all key mapping is working. (When clause was set to enable for spin and spin2 but killed everything instead)
• [F11] key is now assigned as an alternate in case you don't have an [Insert] key (or Fn+Enter is not working)

- Known Issues w/v1.7.1

• We haven't yet learned how to control the ending position of the edit cursor. So in many cases when using selection not an insert point the cursor may end up not being where you might expect it to be after pressing TAB or Shift+TAB. We are looking into how to solve this. Even tho' this problem exists the formatting ability this new service provides is well worth this minor headache. We will keep looking for a means to get this under control.
• 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...

We wish to thank Jay B. Harlow for his contribution to this new feature!

Thank you, Jay, your work is much appreciated!

v1.7.0

Extension Update - Welcome full P1 support! (oh, and a new Insert Mode à la Propeller Tool)

Fun Update! The first release of two NEW features and more.

• NEW P1 support for .spin files (full syntax and semantic highlighting of the P1 language: spin/pasm)
• NEW Add InsertMode support: [Insert|Overwrite|Align]
• More changes to tabbing behavior, we're gradually dialing it in
• P2 Syntax/Semantic highlighting changes - adds support for:
  ● New Spin2 'GETCRC(dataptr,crcpoly,bytecount) method
  ● New Spin2 'STRCOPY(destination,source,maxsize)' method
  ● DEBUG display BITMAP now validates 'SPARSE color'
  ● GRAY, in addition to GREY, now recognized as a color in DEBUG displays

- Known Issues w/v1.7.0

• We need to get Backspace and Delete working correctly when in InsertMode:Align - it's coming, hopefully soon.
• We haven't yet learned how to control the ending position of the edit cursor. So in many cases when using selection not an insert point the cursor may end up not being where you might expect it to be after pressing TAB or Shift+TAB. We are looking into how to solve this. Even tho' this problem exists the formatting ability this new service provides is well worth this minor headache. We will keep looking for a means to get this under control.
• 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...

We wish to thank Jay B. Harlow for his contribution to this new feature!

Thank you, Jay, your work is much appreciated!

v1.6.1

Feature Update - TAB support according to traditional spin2 custom tab-stops à la Propeller Tool

This Update contains the following:

• NEW: Fixes detection of in-line pasm by now treating end correctly and reverting to PUB/PRI tabstop use after the end statement
• NEW: Adds support for asm and endasm FlexSpin in-line pasm keywords
• NEW: adds 3 more tab stops for spin2 code in PUB and PRI (at 12, 14, at 16)
• Adjusts the multiline selection behavior for TAB and Shift+TAB, which is now treating each line individually.

This release fixed multi-line selection bugs in the tabbing support. Both TAB and Shift+TAB now work according to the latest implementation plan

Tabbing support is disabled at first installation. In order to use it you must enable it. Then it will be present when editing any .spin2, or .pasm2 files. NOTE when you enable or disable this feature, please restart VSCode so the change can take effect.

Please let us know of any behavior you are not sure is correct or behavior that just doesn't feel right. Your feedback based on what you are experiencing will help us ensure this is working the way we all would like it to.

New Tabbing Support:

• Supports configurable tab-stops-per-section like Propeller Tool.
• Adds support for single-line indent/outdent
• Adds support for multi-line indent/outdent
• Adds new command Ctrl+Alt+Tab which inserts a current tabs placement comment as a line above the cursor
• This TAB support Spin2 Elastic Tab Stops provides two new settings:
  • Spin2 Elastic Tab Stops:Blocks: is where the tab stops are listed for each section
  • Spin2 Elastic Tab Stops:Enable: checkbox which is by default NOT enabled
    (As this is an early release this feature is not enabled by default. You must enable and then restart vscode)
  • These settings are global but can be edited and made custom per project as well

- Known Issues w/v1.6.1

• We haven't yet learned how to control the ending position of the edit cursor. So in many cases when using selection not an insert point the cursor may end up not being where you might expect it to be after pressing TAB or Shift+TAB. We are looking into how to solve this. Even tho' this problem exists the formatting ability this new service provides is well worth this minor headache. We will keep looking for a means to get this under control.
• The new TAB support does not adhere to INSERT/OVERTYPE/ALIGN modes (will in a later release)
• The single-quote comment (now only on debug statements) is being handled by 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...

We wish to thank Jay B. Harlow for his contribution to this new feature!

Thank you, Jay, your work is much appreciated!

v1.6.0

Feature Update - TAB support according to traditional spin2 custom tab-stops à la Propeller Tool

This release contains:

• Bug fixes to both tab and untab behavior
• NEW now uses DAT tabs for inline pasm
• Adjustment of some behaviors to the new implementation plan

This release fixes bugs in the tabbing support. Both TAB and Shift+TAB now work according to the latest implementation plan

Tabbing support is disabled at first installation. In order to use it you must enable it. Then it will be present when editing any .spin2, or .pasm2 files. NOTE when you enable or disable this feature, please restart VSCode so the change can take effect.

This feature is pretty much ready for use. Please let us know of any behavior you are not sure is correct or behavior that just doesn't feel right. Your feedback based on what you are experiencing will help us ensure this is working the way we all would like it to.

New Tabbing Support:

• Supports configurable tab-stops-per-section like Propeller Tool.
• Adds support for single-line indent/outdent
• Adds support for multi-line indent/outdent
• Adds new command Ctrl+Alt+Tab which inserts a current tabs placement comment as a line above the cursor
• This TAB support Spin2 Elastic Tab Stops provides two new settings:
  • Spin2 Elastic Tab Stops:Blocks: is where the tab stops are listed for each section
  • Spin2 Elastic Tab Stops:Enable: checkbox which is by default NOT enabled
    (As this is an early release this feature is not enabled by default. You must enable and then restart vscode)
  • These settings are global but can be edited and made custom per project as well

- Known Issues w/v1.6.0

• The new TAB support does not adhere to INSERT/OVERTYPE/ALIGN modes (will in a later release)
• The single-quote comment (now only on debug statements) is being handled by 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...

We wish to thank Jay B. Harlow for his contribution to this new feature!

Thank you, Jay, your work is much appreciated!

v1.5.0

Feature Update - add TAB support according to traditional spin2 custom tab-stops à la Propeller Tool

This release provides an early release of the new tabbing support. It is disabled at first installation.
In order to test it you must enable it. Then it will be present when editing any .spin2, or .pasm2 files.
The point of releasing this at this stage is to get an initial review by a couple of interested people in our community. Your feedback based on this review will help us ensure this is working as well as we'd like it to be.

New Tabbing Support:

• Supports configurable tab-stops-per-section like Propeller Tool.
• Adds support for single-line indent/outdent
• Adds support for multi-line indent/outdent
• Adds new command Ctrl+Alt+Tab which inserts a current tabs placement comment as a line above the cursor
• This TAB support Spin2 Elastic Tab Stops provides two new settings:
  • Spin2 Elastic Tab Stops:Blocks: is where the tab stops are listed for each section
  • Spin2 Elastic Tab Stops:Enable: checkbox which is by default NOT enabled
    (As this is an early release this feature is not enabled by default. You must enable and then restart vscode)
  • These settings are global but can be edited and made custom per project as well

- Known Issues w/v1.5.0

• The new TAB support does not adhere to INSERT/OVERTYPE/ALIGN modes (will in a later release)
• The single-quote comment (now only on debug statements) is being handled by 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...

We wish to thank Jay B. Harlow for his contribution to this new feature!

Thank you, Jay, your work is much appreciated!

v1.4.1

Various Highlight fixes and better single-line comment processing

• BUGFIX: (#8) Now correctly recognize assignments within enum declarations
• BUGFIX: (#5) Most of the single-line comments are once again recognized during syntax recognition the remaining exception is when comments following debug() statements
• Now recognize the use of spin2 unary and binary operators within constant assignments
• Fixed a number of small highlight problems: (1) (local variables were not recognized in spin statements), (2) occasionally some comments were processed as spin statements

- Known Issues w/v1.4.1

• The single-quote comment (now only on debug statements) is being handled by 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...

v1.3.9

Minor Highlight fix for unrecognized symbol

• BUGFIX: (#6) correct internal misspelling of X_4P_4DAC1_WFBYTE symbol.

- Known Issues w/v1.3.9

• The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We have don't have a fix for this yet.
• 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...

v1.3.8

Minor semantic pasm highlight fixes

• BUGFIX (#7) - Fix highlighting in pasm statements when using operators with constants. (added missing detection of =,?,:,!, and ^ pasm operators as defined in pasm language manual)

- Known Issues w/v1.3.8

• The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We have don't have a fix for this yet.
• 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...