This problem occurs only if the board selection is Teensy 4.0. If I switch to Teensy 3.6, the wiggly lines go away and Intellisense works.
The code compiles correctly, though.
The problem occurs even with the barest minimum code:
Hovering the mouse over the wiggle shows a message:  variable "EMIT" is not a type name
I have attached a screen capture.

Tim@Visual Micro wrote on Nov 26^th, 2019 at 12:16pm:


Well, on most. Wigglers are: const, int, char, bool, etc., even void.  uint32_t on the other hand  does not have a wiggly.
Also, the wiggles may appear on the first few declarations, then not on a few more, then resume later.

Also, Intellisense works partially, typically typing the first few characters does produce some keywords, but not what 'fits' the context; For instance if you type Ser and press CTRL-SPACE, you would expect to see Serial but instead SerialUSB comes up.
Simply changing the board type drop down to Teensy 3.6 fixes everything.
Please let me know if you need any further information.
Thanks

Thanks for the reports. Yes this can happen with new boards although can sometimes depend on various factors such as if "show all files" is toggled or not.

Anyway we will release an update over the next week that has support for the new teensy toolchain locations.

It is possible to automated the discovery of new toolchains but it has such an overhead that we opt to keep a fast dev environment for now. Maybe in the future when the new teensy toolchain is release we will change. The next Teensy toolchain should be very fast because it's moving to 64 bit and I suspect our virus checkers will be happier about that.

Something you can do that will help is to find the visual micro folder which is shown in vMicro>General>Global Options>System>Assembly

Below that folder is "Micro Platforms\hardware\arduino16x\teensy3"

Copy the teensy3 folder and call it teensy4 which will be a sibling to teensy3:-

"Micro Platforms\hardware\arduino16x\teensy4"

Restart the IDE or click Rescan. If the intellisense has not improved then switch the vMicro menu to use a different board and then reselect the Teensy4.0

Tim@Visual Micro wrote on Nov 27^th, 2019 at 10:59pm:

 
I presume you are referring to the drop down under Tools>Options in Visual Studio.
In my VS2017 install, under vMicro>General>Global Options>System,  there is no Assembly entry.

However, under 
vMicro>General>Global Options>Version, there is an entry for 'Assembly Location' which points to:
c:\program files (x86)\microsoft visual udio.Arduino.15.dll

Stepping up one folder to
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\th3ctv1k.00z
shows a folder called 'Micro Platforms' that contains the following folders, some of which have harware\teensy3 folders.

This is a full list:

arduino10x
arduino15x
arduino16x
arduino19x
arduino_org17x
default
energia
energia16x
intelarduino15x
maple18
mpide
teensy
visualmicro
wiring10x

All the arduino* folders have hardware\teensy3.

Which one should I clone?

BTW, I tried the update to 1911.23.1 for Visual Studio 2017/2019, but I still have the same problem.

Thanks for your prompt response.
Ram

Thanks, Tim!

I had randomly picked one of the folders and cloned it last night, this on a different PC rimming VS2015 - it did not work at first, but this morning (maybe the reboot did it) everything worked great. I am not sure whether the update would work on VS2015, but all is well anyway.

I have not tried that on the VS2017 pc; will try the update again first.
I want to take this opportunity to thank you for the rapidity with which you provide help, not to mentioned your dogged persistence in solving all problems!

Ram