TFT_sSPI vs C/C++ Intellisense

1

Hello All,

During my ‘newbie’ self-teaching I came across this difference in descriptions between the TFT_eSPI reference and Intellisense when it ‘hovers’ over the code for a drawWedgeLine function. It was only by reading the TFT_eSPI reference information I got what the code was trying to do when I built two opposing WedgeLines to form a compass needle.

The TFT_eSPI ‘Rotated_Sprite_2’ example was a great help.

E.g for this code:

cpp

needle.drawWedgeLine(8,40,8,79,6,2,TFT_RED);
  
needle.drawWedgeLine(8,1,8,40,2,6,TFT_BLUE);

```

Intellisense describes this:

void TFT_eSPI::drawWedgeLine(float ax, float ay, float bx, float by, float aw, float bw, uint32_t fg_color, uint32_t bg_color = 16777215U)

TFT_eSPI describes this:

void TFT_eSPI::drawWedgeLine(float ax, float ay, float bx, float by, float ar, float br, uint32_t fg_color, uint32_t bg_color = 0x00FFFFFF)

The subtle difference being float aw and float bw are not the same as float ar and float br when you look at the TFT_eSPI documentation as my understanding is (w) reference line width, (ar) and (br) are for radiused ends which I used for a compass needle.

Does this happen often in intellisense descriptions?

TIA

2

I think this is because IntelliSense is referencing TFT_eSPI.h, where the arguments are listed as aw and bw.
On the other hand, in TFT_eSPI.cpp, they are listed as ar and br, just as you noted.

3

The TFT_eSPI screws this up by using different parameter names in the header file and implementation. Inconsistent.