I hope someone can give a couple of pointers to help debug a Flowcode program I have written for the M5Stack Dial. The program simulates as intended but when compiling I get the Syntax error shown below.
Apart from providing the line number (8378) no other information is given.
My question is how do I identify from the compiler message where the error lies within my flowchart?
The C code just after the reported error line relates to ‘gLCD Font2’. Font 2 was one of the standard fonts provided with FC V11. All that I have done is to call it up within component macros.
I have attached the program which is a pulse generator. When the program is Run in simulation the menu options are selected using a combination of the Quadrature encoder and the Bezel switch.
I am stuck at this point, so any help will be greatly appreciated.
Martin
Compiler Error - ESP M5Stack Dial
-
Arix
- Posts: 16
- http://meble-kuchenne.info.pl
- Joined: Wed Dec 02, 2020 9:53 pm
- Has thanked: 3 times
- Been thanked: 10 times
-
mnfisher
- Valued Contributor
- Posts: 1812
- Joined: Wed Dec 09, 2020 9:37 pm
- Has thanked: 152 times
- Been thanked: 853 times
Re: Compiler Error - ESP M5Stack Dial
I'm not a a computer right now - but you can look at PulseGen v3a.c and look at the offending line - might give some clues (at least which macro the error is in)?
Martin
Martin
Re: Compiler Error - ESP M5Stack Dial
Thank you Martin
That is the area where I am getting stuck. I view the C code file, and in particluar the code around line 8378, but I cannot determine precisely to which component macro command icon it relates.
In the snipit of C code below it appears to relate to the use of Font2 by the gLCD component, which to me looks Ok. I am probably missing the obvious.
That is the area where I am getting stuck. I view the C code file, and in particluar the code around line 8378, but I cannot determine precisely to which component macro command icon it relates.
In the snipit of C code below it appears to relate to the use of Font2 by the gLCD component, which to me looks Ok. I am probably missing the obvious.