Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 [2]  Send TopicPrint
Very Hot Topic (More than 25 Replies) vMicro afther update 86 errors ".. was not declared in this scope" (Read 8576 times)
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12071
Location: United Kingdom
Joined: Apr 10th, 2010
Re: vMicro afther update 86 errors ".. was not declared in this scope"
Reply #20 - Mar 11th, 2022 at 7:37pm
Print Post  
Some later toolchains see a "const" data type as something different, even though it is not. Many older Arduino projects fail to compile because of the "const" issue. Visual Studio doesn't see a difference because the data type is the same. Both are far pointers to a float.

Visual Studio cannot know some finer detail such as that is built into the actual tool chain .exe and is not defined in external sources. For this reasonĀ  Visual Studio can only give 99% accuracy with intellisense. The alternative would be to run the actual tool chain in background while you are coding, that is a huge overhead especially for slower toolchains.

Visual Studio maintains a database for fast intellisense lookups, therefore we have to forgive it some inaccurancy. 

As you have noted, you can rely on the Visual Micro build process to give accurate results because it uses the toolchain directly without involvement from Visual Studio. 

There are other differences you will find between a real build and intellisense. That is because Visual Studio does not understand some of the underlying Gcc code that some toolchains use.

We can improve some areas of intellisense but some areas are beyond what can be achieved. We will look into this but it might be one of those ones we cannot cater for.

« Last Edit: Mar 11th, 2022 at 7:39pm by Tim@Visual Micro »  
Back to top
WWW  
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2145
Joined: Feb 13th, 2019
Re: vMicro afther update 86 errors ".. was not declared in this scope"
Reply #21 - Mar 14th, 2022 at 4:09pm
Print Post  
Thanks for the update.

The errors and code suggestions in Atmel Studio are provided by VisualAssistX, which is not driven directly by Visual Micro.

It seems odd there are no build errors at all for that variable after a build has been run, I would expect a "was not declared in this scope" error from what we can see in the image.
  
Back to top
 
IP Logged
 
Rolf Degen
Junior Member
**
Offline


Posts: 19
Location: Deutschland
Joined: Jul 12th, 2021
Re: vMicro afther update 86 errors ".. was not declared in this scope"
Reply #22 - Mar 15th, 2022 at 1:06pm
Print Post  
Hallo Simon

Current vMicro version causes errors in Teensy 4.1's RAM management. Patches with band-limited PWM waveforms can no longer be loaded. system hangs.  Huh
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2145
Joined: Feb 13th, 2019
Re: vMicro afther update 86 errors ".. was not declared in this scope"
Reply #23 - Mar 23rd, 2022 at 1:14pm
Print Post  
Thanks for the update and apologies for the delay in responding.

Can you enable the verbose and show build properties options as seen at the top of the page, and attach the full build output from your build.

If you have an example simple sketch we can replicate with it will help us understand the issue further.

Does the same happen when uploading the same sketch via the Arduino IDE?
  
Back to top
 
IP Logged
 
Rolf Degen
Junior Member
**
Offline


Posts: 19
Location: Deutschland
Joined: Jul 12th, 2021
Re: vMicro afther update 86 errors ".. was not declared in this scope"
Reply #24 - Mar 23rd, 2022 at 2:38pm
Print Post  
It is probably due to my large program code. The display of free ITCM RAM1 (fast code) in Teensy 4.1 is same with old and new vMicro version. In the old version of vMicro, the code for calculating bandlimited waveforms is faster and doesn't crash. In the new version the code is very slow and the band limited waveforms cannot be calculated fast enough.




« Last Edit: Mar 23rd, 2022 at 2:42pm by Rolf Degen »  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2145
Joined: Feb 13th, 2019
Re: vMicro afther update 86 errors ".. was not declared in this scope"
Reply #25 - Mar 23rd, 2022 at 3:16pm
Print Post  
Thanks for the update and logs.

Can you also send over the "Jeannie.ino.cpp" from the build folder, after building in the old and new versions so we can compare them?

Do you get the same issue in the Arduino IDE when uploading the same program?
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1 [2] 
Send TopicPrint