Updated log, status and beers

Author: elektronikworkshop

BRANCHNOTES.md

@@ -89,6 +89,7 @@ During merging I found some bugs within those functions - mainly due to the abov
 **2020 02 17** Disabled and marked all previous implementations of IntelliSense support for later removal using `IS-REMOVE`. Pulled changes from upstream and merged them into the intellisense feature branch. Began to work on event handling/generation: vscode-arduino should detect when sketch/board/configuration and so on has changed, then re-analyze the current setup and set the IntelliSense configuration accordingly. This works more or less but there's a lot to fix in the current implementation which kept me busy till late today (I need some sleep now). Cleanup and commits follow tomorrow. Approaching alpha version for curious testers. OSX and Linux comes first, Windows will follow later.
 **2020 02 18** Finished basic event triggering. Rewrote `DeviceContext` for proper settings modification detection (trigger events only on actual change) and generation of setting specific events (e.g. board changed) instead of one global event (aka. "something in the settings changed").
 **2020 02 19** Implemented proper build scheduling for analysis build by writing an `AnalysisManager` class. This class collects multiple changes (e.g. board and configuration, which often are changed shortly after another) before running an analysis. In case another build or analysis is in progress it postpones newly filed analysis requests until the other build has completed. Updated and completed the documentation for the IntelliSense usage within [README](README.md). Alpha test builds of the extension containing the latest implemented features and fixes are now available from the following [Dropbox folder](https://www.dropbox.com/sh/whmcdt26chyjgby/AAB1Ld2fzZ9Z_NfM3CRay17wa). Please note, that Windows is currently not supported yet. Reviewed, documented/commented all changes and committed the automatic analysis integration changes.
+**2020 02 20** Windows support - what a PITA. This OS is so foobar'ed... The only positive outcome from this experience: I found some substantial bugs in the parser which - of course (Murphy) - didn't affect me up to now. The parser should be much more resistant against strange paths and escapes now: Added proper command line lexer to cocopa and worked around several ridiculous Windows shortcomings (Microsoft owes me at least 50 crates of beer). The whole mess is not cleaned up and committed yet so please don't build from the repository and use the alpha release packages as outlined above.
 
 ## Status
 |      | Tasks   |
@@ -97,7 +98,7 @@ During merging I found some bugs within those functions - mainly due to the abov
 |                                       | :heavy_check_mark: Support for different boards (done for AVR, ESP32, ESP8266) -- The code has been designed such that it is easy to write/add new parser engines (for non gcc compilers for instance) |
 |                                       | :heavy_check_mark: Getting intrinsic gcc include paths |
 |                                       | :heavy_check_mark: Handling quoted arguments |
-|                                       | :white_check_mark: X-platform support |
+|                                       | :heavy_check_mark: X-platform support |
 | **`c_cpp_properties.json` generator** | :heavy_check_mark: Basic objects |
 |                                       | :heavy_check_mark: Basic setting of parsing result |
 |                                       | :heavy_check_mark: Basic file input  |
@@ -166,6 +167,7 @@ I will list every supporter here, thanks!
 2020-02-17 Elektronik Workshop: 52 :beers: (13h coding)
 2020-02-18 Elektronik Workshop: 36 :beers: (9h coding)
 2020-02-19 Elektronik Workshop: 48 :beers: (12h coding)
+2020-02-20 Elektronik Workshop: 56 :beers: (14h coding)
 
 <!-- https://github.com/StylishThemes/GitHub-Dark/wiki/Emoji -->